Develop Bugs

Samsung Galaxy s3 NOT ROOTED stuck at Logo Screen

I know this has been asked dozens if not hundreds of times, but it seems everyone has bricked their phone by rooting.
My phone has never been rooted, and I have had it working fine for at least 9 months now.
It was working all day and when I got home from school I plugged it into the charger the same as every night and when I woke up it was stuck on the "Samsung Galaxy III" screen.
I have no idea how to fix this please help, I cannot get into recovery mode it just says "recovery 'something'" and disappears quickly then shows the Logo Screen again before shutting off.
I can get into download mode and I guess I have to start from there.
I don't want to do a wipe without at least getting into it in safe mode somehow and backing up some things, please help.
Oh and if it helps no new software was added since the last reboot, the only thing I could think of that changed from it working fine to this morning was my alarm? It was supposed to go off sometime in the morning maybe that froze it up? Other than that I have no idea why it would brick all of a sudden
Here are the screen shots
hxxp://i42.tinypic.com/2rc8nsw.jpg
hxxp://i39.tinypic.com/2zz5dhj.jpg
hxxp://i40.tinypic.com/14bq8lj.jpg
hxxp://i42.tinypic.com/k1f7nt.jpg
{
"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"
}
That was all it said, but if i click to continue then it shows the last 2 screen shots and it stays like that forever.
ODIN MODE
Product Name: SGH-T999
Custom Binary Download: No
Current Binary Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Android icon
Downloading...
Do not turn off target !!

re: stuck screen
tguerrerojr said:
I know this has been asked dozens if not hundreds of times, but it seems everyone has bricked their phone by rooting.
My phone has never been rooted, and I have had it working fine for at least 9 months now.
It was working all day and when I got home from school I plugged it into the charger the same as every night and when I woke up it was stuck on the "Samsung Galaxy III" screen.
I have no idea how to fix this please help, I cannot get into recovery mode it just says "recovery 'something'" and disappears quickly then shows the Logo Screen again before shutting off.
I can get into download mode and I guess I have to start from there.
I don't want to do a wipe without at least getting into it in safe mode somehow and backing up some things, please help.
Oh and if it helps no new software was added since the last reboot, the only thing I could think of that changed from it working fine to this morning was my alarm? It was supposed to go off sometime in the morning maybe that froze it up? Other than that I have no idea why it would brick all of a sudden
Here are the screen shots
hxxp://i42.tinypic.com/2rc8nsw.jpg
hxxp://i39.tinypic.com/2zz5dhj.jpg
hxxp://i40.tinypic.com/14bq8lj.jpg
hxxp://i42.tinypic.com/k1f7nt.jpg
That was all it said, but if i click to continue then it shows the last 2 screen shots and it stays like that forever.
ODIN MODE
Product Name: SGH-T999
Custom Binary Download: No
Current Binary Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Android icon
Downloading...
Do not turn off target !!
Click to expand...
Click to collapse
First I would like to say that if you were to Odin flash the phone with stock T999 or stock
rooted T999 firmware you would not loose anything on your internal or external sdcard.
So my advise would be to do the following:
Here is a 100% sure way to fix the stuck screen on your phone.
Here is the step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you purchased it except for the benefit of being rooted.
Download the stock T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
If you don't want your phone to be rooted then download this instead: http://www.androidfilehost.com/?fid=9390169635556426424
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download ODIN it's required for flashing the stock or stock rooted firmware (a windows app) http://d-h.st/Q14
After it's downloaded extract Odin into the same folder you made containing the T999 TAR file.
Download the stock-rooted Odin flash firmware for the T999 Tmobile Galaxy S3
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!

Misterjunky said:
First I would like to say that if you were to Odin flash the phone with stock T999 or stock
rooted T999 firmware you would not loose anything on your internal or external sdcard.
So my advise would be to do the following:
Here is a 100% sure way to fix the stuck screen on your phone.
Here is the step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you purchased it except for the benefit of being rooted.
Download the stock T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
If you don't want your phone to be rooted then download this instead: http://www.androidfilehost.com/?fid=9390169635556426424
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download ODIN it's required for flashing the stock or stock rooted firmware (a windows app) http://d-h.st/Q14
After it's downloaded extract Odin into the same folder you made containing the T999 TAR file.
Download the stock-rooted Odin flash firmware for the T999 Tmobile Galaxy S3
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!
Click to expand...
Click to collapse
Thank you so much, this worked. But it froze when it started up, not sure if i should have left it longer but after a couple of minutes i pulled the battery and it started doing the original problem again.
i am going to repeat the steps to see if I can get it to boot again like it did initially.

So if i use that first link my phone will be rooted? and if i use the second it will not be rooted?
Not sure if i got that correct, as I have never rooted my phone before

Misterjunky said:
First I would like to say that if you were to Odin flash the phone with stock T999 or stock
rooted T999 firmware you would not loose anything on your internal or external sdcard.
So my advise would be to do the following:
Here is a 100% sure way to fix the stuck screen on your phone.
Here is the step by step guide:
After you have followed these instructions your phone will be in the same condition
as it was the day you purchased it except for the benefit of being rooted.
Download the stock T999 firmware: http://www.androidfilehost.com/?fid=9390169635556426451
If you don't want your phone to be rooted then download this instead: http://www.androidfilehost.com/?fid=9390169635556426424
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download ODIN it's required for flashing the stock or stock rooted firmware (a windows app) http://d-h.st/Q14
After it's downloaded extract Odin into the same folder you made containing the T999 TAR file.
Download the stock-rooted Odin flash firmware for the T999 Tmobile Galaxy S3
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!
Click to expand...
Click to collapse
here is my results
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> recovery.img
<ID:0/003> rpm.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> system.img.ext4
<ID:0/003> tz.mbn
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
but it still isn't working

re: rooted
tguerrerojr said:
So if i use that first link my phone will be rooted? and if i use the second it will not be rooted?
Not sure if i got that correct, as I have never rooted my phone before
Click to expand...
Click to collapse
Yes you are correct the first link is rooted.
Both of the firmwares are STOCK except one is pre-rooted and the other is not.
---------- Post added at 01:10 AM ---------- Previous post was at 01:07 AM ----------
tguerrerojr said:
Thank you so much, this worked. But it froze when it started up, not sure if i should have left it longer but after a couple of minutes i pulled the battery and it started doing the original problem again.
i am going to repeat the steps to see if I can get it to boot again like it did initially.
Click to expand...
Click to collapse
As it says in the bottom of the step by step guide, have patience....
Especially on the first boot.
Once it's fully booted and works normally, I would reboot it once more to start a normal boot cycle.

Misterjunky said:
Yes you are correct the first link is rooted.
Both of the firmwares are STOCK except one is pre-rooted and the other is not.
---------- Post added at 01:10 AM ---------- Previous post was at 01:07 AM ----------
As it says in the bottom of the step by step guide, have patience....
Especially on the first boot.
Once it's fully booted and works normally, I would reboot it once more to start a normal boot cycle.
Click to expand...
Click to collapse
Update: I left it on all night and when I woke up (5 hours later) It was still on the robot screen. I pulled the battery and I am going to wait 30 minutes or so and then try to restart it.

Looks like hardware failure to me.

Aerowinder said:
Looks like hardware failure to me.
Click to expand...
Click to collapse
So what can I do now? Is there anyway to get my stuff or at least boot in safe mode?
i had some important notes in notepad, and some important texts

did you reseat sim and extsd while batt pulled? if not woudn t hurt

Cruze808 said:
did you reseat sim and extsd while batt pulled? if not woudn t hurt
Click to expand...
Click to collapse
Does that help? I will try that next, by reset you mean just pull them out? How long should I leave them out?

re: 30 seconds
tguerrerojr said:
Does that help? I will try that next, by reset you mean just pull them out? How long should I leave them out?
Click to expand...
Click to collapse
30 seconds! just pull em out and replace them just in case one of them is not making good contact./

Hi I am new to all of this but I have followed this guide step by step. I ran odin with the .tar file and clicked start it ran up until
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
it has been like this for the past 3 hours and this is the second time I did this. Do I leave it and let it run longer or do I restart the whole process. My phone is not working at all so I need this to work...PLEASE HELP!!!

re: Odin flash
Rosie5 said:
Hi I am new to all of this but I have followed this guide step by step. I ran odin with the .tar file and clicked start it ran up until
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
it has been like this for the past 3 hours and this is the second time I did this. Do I leave it and let it run longer or do I restart the whole process. My phone is not working at all so I need this to work...PLEASE HELP!!!
Click to expand...
Click to collapse
If I had this problem the first thing I would do is to try a different USB port and a different usb cable.
If you don't have a another usb cable then at least unplug both ends of it and plug it back into the
phone and computer making sure both ends have a good connection then try the odin flash again.
It should take no more than 15 minutes to do a proper odin flash.
Good Luck!

I've tried all the ports in my laptop and used 3 different cables but it still does the same thing

re: try it again.
Rosie5 said:
I've tried all the ports in my laptop and used 3 different cables but it still does the same thing
Click to expand...
Click to collapse
See if you have a friend who has a desktop home computer and try it again.

re:retry
ok so now I give up. I've tried my home pc as well but still nothing. so thanks anyway maybe I should take it to work and have someone else try.

The correct rom
I had this same problem of freezing up on the splash screen. Mine started after installing the carbon rom. I tried all of the steps (and files) here, but none would solve it. The file that finally did is is named T999UVDLJC_T999TMBDLJC_T999UVDLJC_HOME.tar.md5. I can't find it again, but I didn't put a lot of effort into it either (I have it already). I believe this is a complete return to stock, and will give you a clean slate to start over with. Like I said, it worked for me, maybe it will for you too.

Stuck at Boot Screen

Hey guys,
The GT-N7100 of my friend does not boot.It is stuck at the first screen ( Black screen with samsung galaxy note II gt-n7100).
He tried to install a custom rom and installed a Custom Recovery. In Custom Recovery the cache partition couldnt be load. So I cant wipe or format anything. If I want to install a zip, the Recovery just get stuck before even selecting a zip file.
I can access download mode. So I tried to flash another recovery. Odin says successful but the recovery is still the same ????
I also tried to flash a stock rom with Odin... nothing changed
So I dont know what to do next
Please help me!
Thanks in advance

Luke44 said:
Hey guys,
The GT-N7100 of my friend does not boot.It is stuck at the first screen ( Black screen with samsung galaxy note II gt-n7100).
He tried to install a custom rom and installed a Custom Recovery. In Custom Recovery the cache partition couldnt be load. So I cant wipe or format anything. If I want to install a zip, the Recovery just get stuck before even selecting a zip file.
I can access download mode. So I tried to flash another recovery. Odin says successful but the recovery is still the same ????
I also tried to flash a stock rom with Odin... nothing changed
So I dont know what to do next
Please help me!
Thanks in advance
Click to expand...
Click to collapse
well flash philz recovery via odin
untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
now proceed with wipe and after flashing rom ,fix permission and wipe cache and dalvic cache twice then reboot

shhbz said:
well flash philz recovery via odin
untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
now proceed with wipe and after flashing rom ,fix permission and wipe cache and dalvic cache twice then reboot
Click to expand...
Click to collapse
I flashed philz recovery. After pressing the power button just the battery symbol appeared... no reboot. So I treid to boot into the new recovery... but still the old recovery boots
Heres the log from Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_5.11.2-n7100.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> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!

http://forum.xda-developers.com/showpost.php?p=32273406
I wanted to try this, but this download contains just one file. Even if I extract the tar, there are not the files included which are discribed in the thread...
quite strange....
I simply cant flash anything with Odin. Odin says success, but nothing happened to the phone. I didnt read something about people who are having the same issue
This drives me mad .....

Luke44 said:
http://forum.xda-developers.com/showpost.php?p=32273406
I wanted to try this, but this download contains just one file. Even if I extract the tar, there are not the files included which are discribed in the thread...
quite strange....
I simply cant flash anything with Odin. Odin says success, but nothing happened to the phone. I didnt read something about people who are having the same issue
This drives me mad .....
Click to expand...
Click to collapse
well its not sds for sure so it seems either recovery has gone corrupted as,the pit file u said is not required though u can find it here to http://forum.xda-developers.com/showthread.php?t=1896696 post 4 no4 pit file16gb
but i would suggest you to try the recovery thing as mentioned in the link as see as the one i mentioned is used when it does not enter recovery try this version http://d-h.st/vCc
keep the power button pressed it should enter recovery leave the power button when u see samsung logo
I did it long time back so dont remember exactly whether to keep pressing power button or to hold power button worked for me as auto reboot was not working for me so did the other way round as mentioned to you

shhbz said:
well its not sds for sure so it seems either recovery has gone corrupted as,the pit file u said is not required though u can find it here to http://forum.xda-developers.com/showthread.php?t=1896696 post 4 no4 pit file16gb
but i would suggest you to try the recovery thing as mentioned in the link as see as the one i mentioned is used when it does not enter recovery try this version http://d-h.st/vCc
keep the power button pressed it should enter recovery leave the power button when u see samsung logo
I did it long time back so dont remember exactly whether to keep pressing power button or to hold power button worked for me as auto reboot was not working for me so did the other way round as mentioned to you
Click to expand...
Click to collapse
Im glad to hear that it is not sds.
I tried to flash the recovery of your link:
If I leave the phone connected if I press the power button after flashing just the battery symbol apears after a while.
If I disconnect the phone, it tries to boot normal...no recovery...
If I tap on the power button again and again nothing happens.....
If I try to boot into recovery with the 3 button combo there is still the old clockwork recovery.
I also tried to do a emergency recovery with kies. Kies does download all the files and when it starts to flash it gets stuck at 0 % and sais phone is not connected in the right way but it is...
In Odin mode the phone displays
custom binary downloads : Yes ( 1 counts)
But did flash the recovery at least 3 times ...So why does it still display 1

Luke44 said:
Im glad to hear that it is not sds.
I tried to flash the recovery of your link:
If I leave the phone connected if I press the power button after flashing just the battery symbol apears after a while.
If I disconnect the phone, it tries to boot normal...no recovery...
If I tap on the power button again and again nothing happens.....
If I try to boot into recovery with the 3 button combo there is still the old clockwork recovery.
I also tried to do a emergency recovery with kies. Kies does download all the files and when it starts to flash it gets stuck at 0 % and sais phone is not connected in the right way but it is...
In Odin mode the phone displays
custom binary downloads : Yes ( 1 counts)
But did flash the recovery at least 3 times ...So why does it still display 1
Click to expand...
Click to collapse
do u have kies installed when u trying odin if yes then delete it just install the samsung drivers nothing else and disable your antivirus too.
orelse u may try
thats quite strange ok now its time to try the mskip tool just delete all old samsung drivers and kies
and start fresh from here http://forum.xda-developers.com/showthread.php?t=1923956
and as far as the count in concerned its 1 as you were only able to enter recovery once thats why after that u were not able to so as many times u enter custom recovery the count increases

http://forum.xda-developers.com/showthread.php?t=1896696
Do you think it makes sense todo re-partition with the pit file?
There is also a Bootloader to download on this site...

Luke44 said:
http://forum.xda-developers.com/showthread.php?t=1896696
Do you think it makes sense todo re-partition with the pit file?
There is also a Bootloader to download on this site...
Click to expand...
Click to collapse
i would say no until there is an error which shows no pit partition found but after the above steps if it does not then u can give it a fresh start flash the pit first then the firmware . check youtube as how to do it there are vidoes described on how to flash pit and then the firmware.
i would suggest not to do something which you are not sure of and land urself in other issues though flashing pit and firmware is fine but i am not sure about the bootloader maybe u can ask in that specific thread , keten might be the best person to guide you in that case if its safe

shhbz said:
i would say no until there is an error which shows no pit partition found but after the above steps if it does not then u can give it a fresh start flash the pit first then the firmware . check youtube as how to do it there are vidoes described on how to flash pit and then the firmware.
i would suggest not to do something which you are not sure of and land urself in other issues though flashing pit and firmware is fine but i am not sure about the bootloader maybe u can ask in that specific thread , keten might be the best person to guide you in that case if its safe
Click to expand...
Click to collapse
Sorry but I cant find such a viedo...

Luke44 said:
Sorry but I cant find such a viedo...
Click to expand...
Click to collapse
I tried to flsh this, but odin says:
<ID:0/003> Added!!
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

What exact information you can see on Download Mode Rt Upper corner.
post full details here

dr.ketan said:
What exact information you can see on Download Mode Rt Upper corner.
post full details here
Click to expand...
Click to collapse
In the right upper corner is nothing...
In the left upper corner:
ODIN MODE (written in red)
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom

Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG

Luke44 said:
Sorry but I cant find such a viedo...
Click to expand...
Click to collapse
There is I am on phn so would be difficult for me to find but its simple u just select the pit file first in odin and flash keeping ur phn in download mode and then the firmware tar file

Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG
Click to expand...
Click to collapse
I tried a different computer with different cable. On the computer I used this time there is not even kies installed.
Same result as before...

dr.ketan said:
Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG
Click to expand...
Click to collapse
I tried it a few more times..it really doesnt work
Whats wrong with this !"§$%& phone:crying::crying::crying:

[SOLVED] Problems with rooting my Galaxy Note II (model N7100)

[SOLVED] Thanks to dabenaute for great help!
Hi guys!
I tryed to root my Galaxy Note II (model N7100) and something went wrong. I hope you guys can help me. Sorry for my bad english already.
So, I tryed to root my phone using this guide. I do everything like it said and when it was done, my phone opened same satup what was before I started. Because I am noob with this stuff, I think something went wrong. I dont know why, but I decide to make factory reset to my phone.
Then started problems. My phone try to reboot it self but it always stop in flashing Samsung logo.
Then I tryed this guide (1b) but Odin3 stop always in "Get PIT for mapping.."
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
Download mode in my phone says:
"ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: Yes (4 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREW: A2"
What I should try next? I am very grateful every help what I get!

Hello,
to root your phone,download "CF-Auto-Root-t03g-t03gxx-gtn7100.zip" here: http://download.chainfire.eu/264/CF-Root/CF-Auto-Root/CF-Auto-Root-t03g-t03gxx-gtn7100.zip
reboot your phone in download mode
open odin and check "AutoReboot"&"F.Reset Time"
connect your phone(you will see"added")
click on AP or PDA find cf autoroot
click on START and wait
after flash the phone will reboot
that's all,enjoy

dabenaute said:
Hello,
to root your phone,download "CF-Auto-Root-t03g-t03gxx-gtn7100.zip" here:
reboot your phone in download mode
open odin and check "AutoReboot"&"F.Reset Time"
connect your phone(you will see"added")
click on AP or PDA find cf autoroot
click on START and wait
after flash the phone will reboot
that's all,enjoy
Click to expand...
Click to collapse
Done this again and this what happens:
Odin message said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-t03g-t03gxx-gtn7100.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> cache.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
And after that, my phone screen is only black. When I try to open it, it has that "Samsung Galaxy Note II GT-N7100" text awhile and then screens goes black again.
Is my phone now brick?

JukkaP said:
Done this again and this what happens:
And after that, my phone screen is only black. When I try to open it, it has that "Samsung Galaxy Note II GT-N7100" text awhile and then screens goes black again.
Is my phone now brick?
Click to expand...
Click to collapse
please retry and uncheck"Re partition" : Bien:

dabenaute said:
please retry and uncheck"Re partition" : Bien:
Click to expand...
Click to collapse
It was already uncheck.

JukkaP said:
It was already uncheck.
Click to expand...
Click to collapse
sorry i have no other idea its the only way i know and use and it always works for me: (

dabenaute said:
sorry i have no other idea its the only way i know and use and it always works for me: (
Click to expand...
Click to collapse
I appreciat your help! Thanks!
I think that I broke my phone when I tryed factory reset.

JukkaP said:
I appreciat your help! Thanks!
I think that I broke my phone when I tryed factory reset.
Click to expand...
Click to collapse
Im thinking about something...
if you can go into recovery?do it
clear cache and then go into advanced and wipe dalvik cache
reboot
if that fails,go back into recovery and do a wipe factory/reset
and then try thishttp://forum.xda-developers.com/showthread.php?t=1915386

dabenaute said:
Im thinking about something...
if you can go into recovery?do it
clear cache and then go into advanced and wipe dalvik cache
reboot
if that fails,go back into recovery and do a wipe factory/reset
and then try this
Click to expand...
Click to collapse
I go in recovery and cleared cache but I don't understand what you mean by "advanced".
I got these options:
Reboot system now
Apply update from ADB
Apply update from external strorage
Wipe data/factory reset
Wipe cache partiton
Apply update from cache

JukkaP said:
I go in recovery and cleared cache but I don't understand what you mean by "advanced".
I got these options:
Reboot system now
Apply update from ADB
Apply update from external strorage
Wipe data/factory reset
Wipe cache partiton
Apply update from cache
Click to expand...
Click to collapse
hi,"advanced" is an option that you can find if you use philz recovery

dabenaute said:
hi,"advanced" is an option that you can find if you use philz recovery
Click to expand...
Click to collapse
I don't have that. I tryed instal that to my phone but now Odin doesn't even regonize it anymore.

which odin are you using to? you can find the latest philz here:http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100
odin v3.09:http://www.mediafire.com/download/b8w1on8pwd11yby/Odin+v3.09.zip
have you installed the latest drivers for your phone?

dabenaute said:
which odin are you using to? you can find the latest philz here:
odin v3.09:
have you installed the latest drivers for your phone?
Click to expand...
Click to collapse
I use Odin v3.07. I re-installed my phone drivers and boot computer, then odin regonized my phone. I installed philz_touch_6.25.0-n7100.tar.md5
This doesn't help:
dabenaute said:
if you can go into recovery?do it
clear cache and then go into advanced and wipe dalvik cache
reboot
Click to expand...
Click to collapse
Im from Finland, so is there any matter what files I use from here: http://forum.xda-developers.com/showthread.php?t=1915386

i know that thread its usefull,have you made a backup before flashing anything?
have you tried to reflash a stock rom?
---EDIT---
i found this:http://forum.xda-developers.com/showthread.php?t=2700479

dabenaute said:
i know that thread its usefull,have you made a backup before flashing anything?
have you tried to reflash a stock rom?
Click to expand...
Click to collapse
I am lost with that thread. Should I download something or read some adviced? Have to I download some rom?
When I tryed to root my phone, I try to use this guide (sry, that was missing in first post) and I don'n make any backups.
I think I know how to flash (in that thread have good help for that) but Im not sure what to download.

here is a stock rom"n7100xxuemk9"(NEE) 4.3:http://rapidgator.net/file/75b6f9c75caa96166fc0ca6582cf489b
n7100xxuelm3(THL):https://my.pcloud.com/#page=publink&code=XZhg1ZWTIv1SpmTCXVP4bKC0cP0mMWcLNX

Reinstall Complete Stock firmware using Odin & then root
Hi..
Looks like you have got boot loop for while trying to root your phone.
Don't worry.. now you need to reinstall the stock firmware on your device.
just follow the following steps:
1- Boot in recovery by pressing volume up, home button & power button simultaneously
2- go to mounts & storage & then..format system first, then format data & finally format cache
3- Now go back to the main menu of your recovery & do format data/factory reset then format cache & then go to advanced & wipe dalvik cache
4- Download your devices stock firmware from here http://www.sammobile.com/firmwares/1/ ..select your device model & country & download the file...latest firmwares are on top.
5- extract the .zip file you just downloaded & you will get a file with extension .tar.md5
6- Now Boot your device into download mode by pressing Volume down button, home button & power button simultaneously.
7- Launch Odin(v 3.07) now..u can download the attached file. (If the device is detected it will show the COM:# in the ID Com field.)
8- Select the PDA tab & browse & select the firmware file you just extracted.
9- Odin will take a while & finally it will display the message something like checking md5 finished successfully
10- click on the start button & sit back & relax...this may take upto 8 minutes..
11- Unplug the phone after flashing is complete & let the phone boot..
12- Now you will have stock recovery, if you want you will need to flash a custom recovery again.
13- Boot in download mode again & select the PDA tab & browse for the chainfire auto root file (download it from here http://download.chainfire.eu/264/CF-Root/CF-Auto-Root/CF-Auto-Root-t03g-t03gxx-gtn7100.zip )
14- extract the file & select this file from the PDA tab in ODIN & click the Start button.
15- let the flashing complete & the phone will display the recovery mode screen again & it will root the device.
16- However after booting the device you might not be able to open the superuser app.
17- To fix this go to play store & update your SuperSu app & then launch it & then it will ask you to disable Knox & select Yes.
18- Congratulations...your device is now rooted.
Hit thanks if i helped you..Let me know if you face any issues... :good:

dabenaute said:
here is a stock rom"n7100xxuemk9"(NEE) 4.3:http://rapidgator.net/file/75b6f9c75caa96166fc0ca6582cf489b
n7100xxuelm3(THL):https://my.pcloud.com/#page=publink&code=XZhg1ZWTIv1SpmTCXVP4bKC0cP0mMWcLNX
Click to expand...
Click to collapse
Thanks alot! I am very happy because you try to help me out and dont care my stupid questions
I have now downloaded those and now I try to figure out should I use both in flashin? These guides doesn't help me because files are different.
So, where I shoud but those two files in Odin? Is those files enough?

JukkaP said:
Thanks alot! I am very happy because you try to help me out and dont care my stupid questions
I have now downloaded those and now I try to figure out should I use both in flashin? These guides doesn't help me because files are different.
So, where I shoud but those two files in Odin? Is those files enough?
Click to expand...
Click to collapse
try out the steps i have mentioned above in my post..i have also attached the Odin v3.07 & clockwork recovery ver 6 files..
for clcockwork recovery you need to extract the .zip file & you will get a .tar file which you can flash using the PDA tab in odin
this wont take more than 15 minutes & as you will wipe everything you will lose all your apps & contacts..but the data on your internal sd card should remain untouched..

Hello @JukkaP,if you take mk9 you have to decompress it to have 4 files after:
open odin and put
bootloader in the 1st case,2sd ap,3t phone,4th csc
phone in download mod
connect it to the pc
you will have "added"
clic on "start" and wait
phone will reboot after flash
---EDIT----
No question is stupid

[Q] Odin update from 4.3 to 4.4.2 always fail. why?

1. extracted the .tar.md5 file
2. Booted the tablet into Download Mode
3. Connected to the laptop and to the Odin
4. Loaded the tar.md5 file into AP
5. After some minutes, clicked "Start:"
6. Then it said failed
Message box:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P600UEUCND2_P600XARCND2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used the update for "Cellular South" I found some threads that says that is possible.
My note is from Philippines (P600XXUBMJ6)
I enabled USB Debugging Mode
I used the latest Odin. Auto Reboot and F Reset Time checked, others not checked.
I followed every instruction I found but I still failed to update
Help
EDIT: It seems to have problem with the PIT. But I didn't check re-partition.

Are you using a full factory firmware?

buhohitr said:
Are you using a full factory firmware?
Click to expand...
Click to collapse
I don't know actually. I just downloaded the file from Sammobile.
Sent from my SM-P600 using XDA Free mobile app

ivanskie01 said:
I don't know actually. I just downloaded the file from Sammobile.
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
You have stock rom installed right now right? What is the build of your 4.3 rom? I would try Odin 3.09 and another firmware (maybe the same 4.3 stock rom that you currently installed) to see what's going on...

buhohitr said:
You have stock rom installed right now right? What is the build of your 4.3 rom? I would try Odin 3.09 and another firmware (maybe the same 4.3 stock rom that you currently installed) to see what's going on...
Click to expand...
Click to collapse
Yes I have stock rom installed. Unrooted. Build is JSS15J.P600XXUBMJ6. This rom is the one already installed in my note when I bought it. EDIT: I found this in Sammobile. It might help: http://www.sammobile.com/firmwares/1/?model=SM-P600&pcode=XTC#firmware
I tried to flash the the kitkat rom from Cellular South and Spain. Both didn't work.
Thanks for your time helping me

sure you run ODIN as administrator ?

lightman33 said:
sure you run ODIN as administrator ?
Click to expand...
Click to collapse
Yes I'm sure. Right click then run as administrator then allow

UPDATE: I tried flashing again using Odin. This time I removed everything connected via USB including the mouse. Still, no luck

ivanskie01 said:
1. extracted the .tar.md5 file
2. Booted the tablet into Download Mode
3. Connected to the laptop and to the Odin
4. Loaded the tar.md5 file into AP
5. After some minutes, clicked "Start:"
6. Then it said failed
Message box:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P600UEUCND2_P600XARCND2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used the update for "Cellular South" I found some threads that says that is possible.
My note is from Philippines (P600XXUBMJ6)
I enabled USB Debugging Mode
I used the latest Odin. Auto Reboot and F Reset Time checked, others not checked.
I followed every instruction I found but I still failed to update
Help
EDIT: It seems to have problem with the PIT. But I didn't check re-partition.
Click to expand...
Click to collapse
I think you first need to get a 4.4 supported kernel when updating to KitKat from JB...atleast that's what you gotta do when flashing from recovery...

ivanskie01 said:
UPDATE: I tried flashing again using Odin. This time I removed everything connected via USB including the mouse. Still, no luck
Click to expand...
Click to collapse
Can you provide a link where you found the CelluarSouth 4.4 firmware??

The Dork Knight Rises said:
I think you first need to get a 4.4 supported kernel when updating to KitKat from JB...atleast that's what you gotta do when flashing from recovery...
Click to expand...
Click to collapse
I'm flashing from Odin, not from recovery
Sent from my SM-P600 using XDA Free mobile app

buhohitr said:
Can you provide a link where you found the CelluarSouth 4.4 firmware??
Click to expand...
Click to collapse
Here it is: http://www.sammobile.com/firmwares/3/?download=28717
Sent from my SM-P600 using XDA Free mobile app

ivanskie01 said:
Here it is: http://www.sammobile.com/firmwares/3/?download=28717
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
It seem to be the full firmware for your p600. I would do a factory reset and try different usb port on your pc (do not use hub). If that still doesn't work give another 4.4 firmware a try to see if firmware related issue. Good luck!

buhohitr said:
It seem to be the full firmware for your p600. I would do a factory reset and try different usb port on your pc (do not use hub). If that still doesn't work give another 4.4 firmware a try to see if firmware related issue. Good luck!
Click to expand...
Click to collapse
I'll try again tomorrow thanks!
Sent from my SM-P600 using XDA Free mobile app

UPDATE
I did the factory reset but still, I can't flash the kitkat firmware.
I also noticed that after one try of flashing and I click the reset button in Odin, the process gets stucked at "SetupConnections". Is this a bug in Odin 3.09 or should I download another Odin?

UPDATE
I tried rooting my note by following this: http://forum.xda-developers.com/showthread.php?t=2490805
I got the same "PIT Mapping issue" and failed.
I also tried flashing a custom recovery via Odin, and failed.
I tried using different downloads of Odin, same issues.
Now I don't know if something's wrong with my Note or my laptop or the USB ports of my laptop.
Help

ivanskie01 said:
I'm flashing from Odin, not from recovery
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
But the method still remains the same, doesn't it? Try flashing a supported kernel first...
Take a nandroid though...

ivanskie01 said:
1. extracted the .tar.md5 file
2. Booted the tablet into Download Mode
3. Connected to the laptop and to the Odin
4. Loaded the tar.md5 file into AP
5. After some minutes, clicked "Start:"
6. Then it said failed
Message box:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P600UEUCND2_P600XARCND2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used the update for "Cellular South" I found some threads that says that is possible.
My note is from Philippines (P600XXUBMJ6)
I enabled USB Debugging Mode
I used the latest Odin. Auto Reboot and F Reset Time checked, others not checked.
I followed every instruction I found but I still failed to update
Help
EDIT: It seems to have problem with the PIT. But I didn't check re-partition.
Click to expand...
Click to collapse
@ The Dork Knight Rises: Nah...to flash a supported kernel first..makes absolutely no sense in odin mode no kernel is running. The update needs to flash a new bootloader in order to be able to boot 4.4 and that can cause trouble.
When having Samsung kies installed, de-install it and reboot windows
Install these USB drivers(They are issued for the verizon P605, but that says that these are the right generation they are not device specific): http://www.samsung.com/us/support/owners/product/SM-P605VZKEVZW
And reboot windows. Make sure no antivirus is running whilst flashing.
Boot your tab into stock recovery (power+volume up) and make a data/factory reset there.
Let the tab boot up the old Android 4.3 until it prompts you for input.
Switch it completely off.
Hard boot into Odin mode pressing power+volume down, choose download mode. No other way! No soft boot into it!
Open odin 3.09 as admin
Connect tab and wait until you get a blue sign in Odin and drivers have been installed completely.
Add the firmware file to AP / PDA wait until odin is ready (no spinning circle).
Make sure re-partition is not ticked
Click the start button, sit back and wait a few minutes
After the FW has been flashed the tab reboots into stock recovery first (probably to update the BL) and then into Android 4.4, let it connected until Android is up and running.
If it is not working try another PC .Alternatively try the one from Spain it is also an XX firmware as your 4.3 and has open CSC (OXA) as well.
Make sure you are following these steps closely and chronologically!

Vaira said:
@ The Dork Knight Rises: Nah...to flash a supported kernel first..makes absolutely no sense in odin mode no kernel is running. The update needs to flash a new bootloader in order to be able to boot 4.4 and that can cause trouble.
When having Samsung kies installed, de-install it and reboot windows
Install these USB drivers(They are issued for the verizon P605, but that says that these are the right generation they are not device specific): http://www.samsung.com/us/support/owners/product/SM-P605VZKEVZW
And reboot windows. Make sure no antivirus is running whilst flashing.
Boot your tab into stock recovery (power+volume up) and make a data/factory reset there.
Let the tab boot up the old Android 4.3 until it prompts you for input.
Switch it completely off.
Hard boot into Odin mode pressing power+volume down, choose download mode. No other way! No soft boot into it!
Open odin 3.09 as admin
Connect tab and wait until you get a blue sign in Odin and drivers have been installed completely.
Add the firmware file to AP / PDA wait until odin is ready (no spinning circle).
Make sure re-partition is not ticked
Click the start button, sit back and wait a few minutes
After the FW has been flashed the tab reboots into stock recovery first (probably to update the BL) and then into Android 4.4, let it connected until Android is up and running.
If it is not working try another PC .Alternatively try the one from Spain it is also an XX firmware as your 4.3 and has open CSC (OXA) as well.
Make sure you are following these steps closely and chronologically!
Click to expand...
Click to collapse
Thanks for the instructions ) I'll try to do this before classes start )
Sent from my SM-P600 using XDA Free mobile app

ivanskie01 said:
Thanks for the instructions ) I'll try to do this before classes start )
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
Be aware that this process wipes all your installed apps and personal data. Also make sure that you are using the original USB cable that came with your device and make sure the device is fully charged.
Start with those steps when your tab has been switched off. With hard boot I mean to boot using key combination, no boot using reboot menu. Be sure you are in download mode where the green android / Knox flag is shown before you connect the tab with your PC.
It worked for me exactly this way. Although I have the P605 (no verizon edition). The provided Samsung drivers should be the right for you as well, good luck.

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

Hey guys, made an account just to ask this question as every time I try to flash CWM or TWRP my tab 3 just fails to do it
I follow all the instructions,
Boot into download mode
select the file in odin 3.07
deselect auto reboot
click start
I then tried all different combinations of buttons, i.e Power+vol up
but when I do that, unless I boot back into android, it just perpetually resets and wont go into recovery mode
Am I missing something here? a prerequisite?

Did you try the combination Volume+ and Home and PowerOn, after you see the Samung Galaxy Logo, let go off the Power-Button and keep holding Volume+ and Home?
This ist the (Custom-)Recovery Mode, Power and Vol- would be Download-Mode.

Pitey said:
Did you try the combination Volume+ and Home and PowerOn, after you see the Samung Galaxy Logo, let go off the Power-Button and keep holding Volume+ and Home?
This ist the (Custom-)Recovery Mode, Power and Vol- would be Download-Mode.
Click to expand...
Click to collapse
When I try the Vol+, power on and home it does the exact same thing, except resets once and then boots in to android

@AppleAssassin
First you are going to READ All this before executing anything. It took me a long time to write this, you should at least read it.
Please understand that we can not disconnect the battery!! So every time we press the POWER longer than 5 seconds TAB mimics a battery disconnect. Guess what, if you let the power button pressed after "Samsung" Logo shows, it will power of again!! This is what I suspect is your problem!!!!!!!!!!!!!!!!!!!!!!. One you see Samsung Logo you need to release the Power.
Also, The original Command for Samsung Download Mode is [Power]+[Volume Down]+[Menu]. But in fact mine just go in Download without [Menu], just [Power]+[Volume Down] and release after Samsung logo.
Since our TAB 10 has a big screen it makes a little difficult to navigate on recoveries. I found that the best is a CWM improve version called Philz Adv CWM 6.55.0. You can read moonbutt74 tread at http://forum.xda-developers.com/gal...ockworkmod-recovery-6-0-5-0-gt-p5210-t2830871
This will send you to: h__p://d-h.st/users/moonbutt74/?fld_id=38524#files
And I will suggest you download =>http://fs1.d-h.st/download/00136/SSY/PhilzAdvCWM-6_55_0-gtP-5210-v2.zip
1)First you need to feel comfortable. Realize that your tablet screen is a BIGGG button. Once you are doing the Dangerous stuff, if you have butter hands you can get in trouble easily. I do preferred to work with my TAB3 in a Flat surface like a table. Hands away if you do not need to touch anything.
2)Google and Youtube is your friend. I try to search for a video on TAB3 10 Recovery but no luck. So please look at:
Samsung Galaxy Tab 3 ClockWorkMod Recovery Install =>http://www.youtube.com/watch?v=XolmtyvS3Yk&feature=youtu.be
That is for a 7" instead of a 10". You only need to realize that the [MENU Button] is on the side in a 7#. TAB3 10" [MENU Button] is on in the bottom (Land Scape). Use ONLY the software that applied to you particular model. Ignore the software names of the video.
You can have more videos at:
[VIDEOS] Galaxy Tab 3 7in How to root, recovery, roms, & Kitkat=>http://forum.xda-developers.com/showthread.php?t=2459817
3)First turn on Tab and in Android OS Play with your buttons and verify they work. Learn to know what is your [Power] [Volume Down] [Volume Up] & [Menu]. Set clear in your mind that the [Volume Down] is the closes to the [Power].
4) If anything Fails you can get in to Download mode with adb command. But Please note that I will suggest you to figure out first why the volume method is not working, you will need them in the future. Be smart!.
See this video =>http://www.youtube.com/watch?v=NPYCpbMoWkQ
It show you how to use Googles SDK adb. Downloading SDK takes for ever. This what I will sugest you use. Instead use "Minimal ADB" by going to to this page http://forum.xda-developers.com/showthread.php?t=2317790 READ that page too.
Download Version 1.1.3 for windows =>https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing
As you will found installation will create a Shortcut in you Desktop. Using that "Minimal ADB and Fastboot" Shortcut will make the first 5 minutes of the previous video useless. So you only need the last minute where you type "adb reboot download". But here is my explanation:
a) Hook your Tab3 to the PC
b) Use "Minimal ADB and Fastboot" Shortcut
c) Verify that you Tab3 is recognized. Type in "Minimal ADB" the command
Code:
[COLOR="Blue"]adb device[/COLOR]s
If you find your self with this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>[COLOR="Blue"]adb devices[/COLOR]
List of devices attached
12345678901234 [COLOR="Red"]offline[/COLOR]
This means you device is offline. To repair go to: Settings>Developer Options>
Now Unselected "Usb Debugging option" and reselect.
A Windows Pop Up, Click "Ok"
now lets try again adb devices
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
12345678901234 [COLOR="Blue"]device[/COLOR]
Success! is connected.
d) Now type in the Minimal ADB CMD window "adb reboot download" [Enter]
Code:
adb reboot download
You will see your tab turn off and reboot in Download mode. Now you can use Odin.

r2d23cpo said:
@AppleAssassin
First you are going to READ All this before executing anything. It took me a long time to write this, you should at least read it.
Please understand that we can not disconnect the battery!! So every time we press the POWER longer than 5 seconds TAB mimics a battery disconnect. Guess what, if you let the power button pressed after "Samsung" Logo shows, it will power of again!! This is what I suspect is your problem!!!!!!!!!!!!!!!!!!!!!!. One you see Samsung Logo you need to release the Power.
Also, The original Command for Samsung Download Mode is [Power]+[Volume Down]+[Menu]. But in fact mine just go in Download without [Menu], just [Power]+[Volume Down] and release after Samsung logo.
Since our TAB 10 has a big screen it makes a little difficult to navigate on recoveries. I found that the best is a CWM improve version called Philz Adv CWM 6.55.0. You can read moonbutt74 tread at http://forum.xda-developers.com/gal...ockworkmod-recovery-6-0-5-0-gt-p5210-t2830871
This will send you to: h__p://d-h.st/users/moonbutt74/?fld_id=38524#files
And I will suggest you download =>http://fs1.d-h.st/download/00136/SSY/PhilzAdvCWM-6_55_0-gtP-5210-v2.zip
1)First you need to feel comfortable. Realize that your tablet screen is a BIGGG button. Once you are doing the Dangerous stuff, if you have butter hands you can get in trouble easily. I do preferred to work with my TAB3 in a Flat surface like a table. Hands away if you do not need to touch anything.
2)Google and Youtube is your friend. I try to search for a video on TAB3 10 Recovery but no luck. So please look at:
Samsung Galaxy Tab 3 ClockWorkMod Recovery Install =>http://www.youtube.com/watch?v=XolmtyvS3Yk&feature=youtu.be
That is for a 7" instead of a 10". You only need to realize that the [MENU Button] is on the side in a 7#. TAB3 10" [MENU Button] is on in the bottom (Land Scape). Use ONLY the software that applied to you particular model. Ignore the software names of the video.
You can have more videos at:
[VIDEOS] Galaxy Tab 3 7in How to root, recovery, roms, & Kitkat=>http://forum.xda-developers.com/showthread.php?t=2459817
3)First turn on Tab and in Android OS Play with your buttons and verify they work. Learn to know what is your [Power] [Volume Down] [Volume Up] & [Menu]. Set clear in your mind that the [Volume Down] is the closes to the [Power].
4) If anything Fails you can get in to Download mode with adb command. But Please note that I will suggest you to figure out first why the volume method is not working, you will need them in the future. Be smart!.
See this video =>http://www.youtube.com/watch?v=NPYCpbMoWkQ
It show you how to use Googles SDK adb. Downloading SDK takes for ever. This what I will sugest you use. Instead use "Minimal ADB" by going to to this page http://forum.xda-developers.com/showthread.php?t=2317790 READ that page too.
Download Version 1.1.3 for windows =>https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing
As you will found installation will create a Shortcut in you Desktop. Using that "Minimal ADB and Fastboot" Shortcut will make the first 5 minutes of the previous video useless. So you only need the last minute where you type "adb reboot download". But here is my explanation:
a) Hook your Tab3 to the PC
b) Use "Minimal ADB and Fastboot" Shortcut
c) Verify that you Tab3 is recognized. Type in "Minimal ADB" the command
Code:
[COLOR="Blue"]adb device[/COLOR]s
If you find your self with this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>[COLOR="Blue"]adb devices[/COLOR]
List of devices attached
12345678901234 [COLOR="Red"]offline[/COLOR]
This means you device is offline. To repair go to: Settings>Developer Options>
Now Unselected "Usb Debugging option" and reselect.
A Windows Pop Up, Click "Ok"
now lets try again adb devices
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
12345678901234 [COLOR="Blue"]device[/COLOR]
Success! is connected.
d) Now type in the Minimal ADB CMD window "adb reboot download" [Enter]
Code:
adb reboot download
You will see your tab turn off and reboot in Download mode. Now you can use Odin.
Click to expand...
Click to collapse
Hey, thanks for writing all that but the problem isn't getting in to download mode. It's after I use odin in download mode. Whether I use "Auto Reboot" or manually reboot. Neither work. If I manually reboot out of download mode after I flash using odin, using the power+vol up and then release the power button as soon as I see the samsung logo it reboots again and then boots into android.

AppleAssassin said:
Hey, thanks for writing all that but the problem isn't getting in to download mode. It's after I use odin in download mode. Whether I use "Auto Reboot" or manually reboot. Neither work. If I manually reboot out of download mode after I flash using odin, using the power+vol up and then release the power button as soon as I see the samsung logo it reboots again and then boots into android.
Click to expand...
Click to collapse
So the problem is in fact You Can Not get into Recovery Mode!
My best guest is that the recovery file you are using is no good or that the procedure using Odin is no good.
Before we do anything lets use ADB Minimal to go into Recovery Mode and see what is the output.
So lets do Step #4 of my previous tutorial. But the last command instead of "adb reboot download" you are going to do
Code:
adb reboot recovery
Tel me what you see without pushing any buttons.

r2d23cpo said:
So the problem is in fact You Can Not get into Recovery Mode!
My best guest is that the recovery file you are using is no good or that the procedure using Odin is no good.
Before we do anything lets use ADB Minimal to go into Recovery Mode and see what is the output.
So lets do Step #4 of my previous tutorial. But the last command instead of "adb reboot download" you are going to do
Code:
adb reboot recovery
Tel me what you see without pushing any buttons.
Click to expand...
Click to collapse
I can boot recovery mode when the device has been turned off using power+vol up but I cannot reboot in to recovery from download mode. I can also reboot into recovery OR download mode using the adb fastboot

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?

AppleAssassin said:
I can boot recovery mode when the device has been turned off using power+vol up but I cannot reboot in to recovery from download mode. I can also reboot into recovery OR download mode using the adb fastboot
Click to expand...
Click to collapse
Boy o Boy, you have no problem!
You are just complaining about Odin. Why Odin is not allowing you to reboot into recovery form it self! For that I have no Idea. Normally I used Odin ones to get my first Recovery and no more! I could used it again to load a factory OS, but I do not see my self doing that soon. The rest I do it from recovery using update.zip.

r2d23cpo said:
Boy o Boy, you have no problem!
You are just complaining about Odin. Why Odin is not allowing you to reboot into recovery form it self! For that I have no Idea. Normally I used Odin ones to get my first Recovery and no more! I could used it again to load a factory OS, but I do not see my self doing that soon. The rest I do it from recovery using update.zip.
Click to expand...
Click to collapse
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

AppleAssassin said:
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?
Click to expand...
Click to collapse
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/SuperSU/UPDATE-SuperSU-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!
AppleAssassin said:
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
Click to expand...
Click to collapse
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.

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.

r2d23cpo said:
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/SuperSU/UPDATE-SuperSU-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.
Click to expand...
Click to collapse
It works!

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.

r2d23cpo said:
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.
Click to expand...
Click to collapse
I encountered the same problem. Thanks to your solution i could solve it. Thank you very much.

Hello, I rooted with odin and put in philz recovery and had SU 2.02 working but then I wanted to try pimpdroid, so I cleared the data for a fresh install as described and then tried to install pimpdroid...nothing happens just Samsung boot screen forever... Tried to go back to SU still nothing...tried to factory reflash and the same...did I brick this thing somehow or anyone can tell me what to do? It's the Canadian version. Was starting with 4.42.
HELP!! PLEAAAAZE?!?!!?