Android OS Forum banner
Cancel
Create thread New Forums

[How To] Rooting GT-P3113 Step-by-Step (Updated 07/18/2012)

Tags
p3113
Jump to Latest
160K views 145 replies 59 participants last post by  krumple  
#1 · (Edited by Moderator)
Credits
xoomdev for his 5.5.0.4 CWM Recovery.
codeworkx for 5.5.0.4 CWM Recovery. <------ Recommended
nycbjr for the CWM Root and the TWRP Touch Recovery.
jcase for the Unsecured Boot Images.
imnuts for espresso_recovery.tar.md5 with unsecured boot.img without recovery overwrite.
Team Win Recovery Project (link) for their work on the TWRP Recovery.

Files
espressowifi-recovery-5-18.tar.md5 - Use if running UEALCB, UEALD3 or UEBLG2 firmware out of the box. (xoomdev)

espresso_recovery.tar.md5 - Use if tablet has been updated OTA to UEALD3, or has UEALD3 and not sure if it was updated OTA. Includes insecure UEALD3 boot.img w/o recovery overwrite. (imnuts)

ueblg2_espressowifi_recovery.tar.md5 - Use if tablet has been updated OTA to UEBLG2, or has UEBLG2 and not sure if it was updated OTA. Includes insecure UEBLG2 boot.img without recovery overwrite. (winterwar)

ueblg5_espressowifi_recovery.tar.md5 - Use if tablet has been updated OTA to UEBLG5, or has UEBLG5 and not sure if it was updated OTA. Includes insecure UEBLG5 boot.img without recovery overwrite and codeworkx 5.5.0.4 recovery. (winterwar)

ueblh1_espressowifi_recovery.tar.md5 - Use if tablet has UEBLH1 installed. Includes insecure UEBLH1 boot.img without recovery overwrite and codeworkx 6.0.1.0 recovery.

ueblh2_espressowifi_recovery.tar.md5 - Use if tablet has UEBLH2 installed. Includes insecure UEBLH2 boot.img without recovery overwrite and codeworkx 6.0.1.0 recovery.

Download cwm-root-gtab2.zip (nycbjr)

Download Odin3-v1.85_3.zip

Samsung Drivers - Not required if you have Samsung Kies installed. These are the same drivers that are included with Kies.

Root
Copy cwm-root-gtab2.zip to the ROOT of your sdcard ( /mnt/extSdCard ). This is the sdcard in the slot. The /mnt/sdcard folder is in the internal memory and isn't recognized by xoomdev's recovery.

Turn off your tablet and restart it in download mode by pushing and holding down the Power and Volume DOWN buttons at the same time. Push the Volume UP to get into download mode. Don't plug the tablet into the computer yet.

If you installed Samsung's Kies software, make sure it is closed and not running.

Extract Odin3 v1.85.exe and run it.

Connect the tablet to the computer.

The first box under ID:COM will be yellow and shows the current com port you are connected to. If you can't connect, try another USB port.

In Odin, click the PDA button. Select the *.tar.md5 file you downloaded above and click the START button. Let Odin do it's thing. When it's done, the tablet will reboot.

Disconnect the tablet from the computer. Turn the tablet off and restart it in recovery mode by pushing and holding the Power and Volume UP buttons at the same time.

Once you are in recovery, use the volume button to scroll up/down and the power button to select an option. Select install zip from sdcard. Choose the cwm-root-gtab2.zip file you already copied to the root of the sdcard.

When the rooting is finished, choose reboot system now in the recovery menu.

That's it. If everything went well, you should now be rooted.

Optional Flashable Recoverys
Flash these zip files through recovery manager.

codeworkx_recovery.zip - Latest Clockwork Recovery from codeworkx.

twrp-recovery-gt3110.zip - TWRP Touch Recovery from nycbjr and TWRP.

espressowifi-recovery-5-18.zip - Recovery included in tar packages from xoomdev.

(!)
 
N
#4 · (Edited by Moderator)
how long its should take to finish this step?

"In Odin, click the PDA button. Select the recovery.tar.md5 file you downloaded and click the START button. Let Odin do it's thing. When it's done, the tablet will reboot."

The message is still

<OSM> Enter CS for MD5..
<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..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!

EDIT: its ok now.

Thanks.
 
#6 · (Edited by Moderator)
EDIT:
The Odin output above is the result if you weren't connected to the tablet. Make sure that the first box under ID:COM is yellow and shows the com port you are connected to.

That process should only take a few seconds to finish. It sounds like you were finally able to get connected and download completed without error. No need for Odin after that.
 
Save
Reply Quote Like Like
#7 · (Edited by Moderator)
slopokdave said:
Thank you, Winterwar!! Worked perfect. Question:

My Tab came with [background=rgb(245, 245, 245)]UEALD3, do I now have to do the steps in this thread to keep CWM? ([/background]http://rootzwiki.com...very-overwrite/)

-Dave
Click to expand...
That's the same firmware that my GT2 came with and it hasn't been a problem. From what I understand, the thread above by jcase only applies if your tablet received a firmware update after you got it. If you had UEALCB originally and it updated to UEALD3, then you would need to follow his directions.

Someone correct me if I'm wrong...
 
Save
Reply Quote Like Like
M
#9 ·
Noob problem here.
I followed the directions step by step, but get "E:signature verification failed" in the system recovery mode.

<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> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!

I updated from P3113UEALCB to P3113UEALD3 before attempting root, does that make any difference? I have tried multiple times with the same results. I apologize if this is a stupid question, I appreciate any help. Thanks.
(im off to work now, but will check back ASAP)
 
#13 ·
Monte2 said:
Noob problem here.
I followed the directions step by step, but get "E:signature verification failed" in the system recovery mode.

<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> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!

I updated from P3113UEALCB to P3113UEALD3 before attempting root, does that make any difference? I have tried multiple times with the same results. I apologize if this is a stupid question, I appreciate any help. Thanks.
(im off to work now, but will check back ASAP)
Click to expand...
The CWM Recovery is installing, but it's being over written by the stock recovery. This happens if you have updated using the OTA prior to rooting. Follow jcase's thread at this link to fix the problem: http://rootzwiki.com/topic/24762-stopping-recovery-overwrite/

If you need Heimdall, you can download it here: http://www.glassechidna.com.au/products/heimdall/
 
  • Like
Reactions: Monte2
Save
Reply Quote Like Like
J
#14 · (Edited by Moderator)
I rooted last night but have made no changes as of yet, how do I actually know I am rooted? The only indication is the word modified under device status.
When I put a ROM on the tablet is it done just like the Thunderbolt? That is place the ROM zip on the Ext SD card and after restarting in Recovery follow the path to loading the file. Is that right?
 
#16 ·
Look in your apps and see if SuperUser is installed. Installing a new ROM is just like on the Thunderbolt.
 
Save
Reply Quote Like Like
N
#17 ·
Guess I am not allowed root. Colored steps but can't get into clockwork....always android recovery....any pointers?

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
 
Save
Reply Quote Like Like
J
#20 ·
Thank you for the assistance in rooting this tablet. I did the deed about 24 hours ago and though I have not loaded a new ROM yet I will as soon as I see a stable ROM that appeals to me. I recommend rooting to anyone who is reluctant, just follow the sequence carefully.
Thanks again for all the help.
 
R
#21 ·
Hey guys, so for some reason I can't get Odin to work - hoping somebody can point me in the right direction. Here's where I'm at.

-- Galaxy Tab 2 7.0 running the UEALCB firmware
-- Following this thread: http://rootzwiki.com...very-overwrite/ , I successfully flashed the unsecured boot image corresponding to my firmware package using Heimdall.
-- Now when I boot my Tab into download mode, the top left says "YES (1 counts)" for custom binary download, and says "CUSTOM" for current binary.

However, when I follow the steps in the OP in this thread, in Odin I get the output shown by nohctis upthread:

<OSM> Enter CS for MD5..
<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..
<OSM> All threads completed. (succeed 0 / failed 0)

After reading the responses here, it sounds like I'm supposed to be seeing the box under ID:COM show yellow with a COM port listed in Odin -- but I'm not. With Heimdall, my device is being detected just fine, on frontend and in command line. I've tried restarting the computer and the tab, and I've tried different USB ports.

Anybody have any idea what I'm missing here? Many thanks in advance.
 
#22 ·
Rhayader said:
After reading the responses here, it sounds like I'm supposed to be seeing the box under ID:COM show yellow with a COM port listed in Odin -- but I'm not. With Heimdall, my device is being detected just fine, on frontend and in command line. I've tried restarting the computer and the tab, and I've tried different USB ports.

Anybody have any idea what I'm missing here? Many thanks in advance.
Click to expand...
You are right you should see yellow in the box.

make sure Samsung Keis driver is installed and then go into device manger and unistall the samsung device in the manager window. Now under device manger and action select "scan for harware changes" it should re-discover your tablet and the ODIN window should turn yellow.

I have a couple of phones and this tablet and I have to jiggle my setup time and time again to get the system to use the correct driver.

I put my device into download mode and start ODIN and then jiggle my device manager until I get the right driver loaded. I am sure there is a windows app to check and apply the correct driver but this works for me.

It seems that after loading the driver for Heimfall you need to get back to the Samsung driver.

Good luck.
 
R
#25 · (Edited by Moderator)
hello all
need some help root my tab
i did the Odin and i get

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<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/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/003> Added!!

am i doing it right. but i am not get the ClockworkMod Recovery setup so i can root my tab 2
 
#26 ·
That looks right. Did you flash the zip file from recovery?
 
Save
Reply Quote Like Like
#28 · (Edited by Moderator)
It sounds like your tablet may have had the OTA firmware update installed. If that's the case, you need to follow this thread and use the instructions under post number seven (#7): http://rootzwiki.com...te/#entry663213

You can download Heimdall from here: http://www.glassechi...ducts/heimdall/

Once you have done that, you can reflash CWR using Odin and then flash the zip file for root.
 
Save
Reply Quote Like Like
A
#30 ·
[background=rgb(245, 245, 245)]I want to[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]do and I[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]root[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]the[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]tablets[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]but[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]I[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]have the[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]following problem[/background][background=rgb(245, 245, 245)].[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]When[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]I get into[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]my[/background][background=rgb(245, 245, 245)]rekovery[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]mode[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]does not[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]show the[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]option[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]"install zip from sdcard".[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]The installation[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]file[/background][background=rgb(245, 245, 245)]"recovery.tar.md5"[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]was successful.[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]Please[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]how can I[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]overcome[/background][background=rgb(245, 245, 245)] [/background][background=rgb(245, 245, 245)]this problem[/background][background=rgb(245, 245, 245)];[/background]
 
#33 ·
Updated the OP to include the recovery package from imnuts. Hopefully, this will eliminate the need for Heimdall and stop some of the confusion and frustration for anyone that updated to UEALD3 from UEALCB with the OTA.
 
Save
Reply Quote Like Like
B
#35 ·
Sorry if this is a noob question, but I have never rooted anything before or had an Android device. Do I download these files on the tablet or my laptop? I have all the files on the laptop desktop at the moment. Also I was reading the steps and it says something about an SD card, mine has an mini SD card slot, but no mini SD card in it?
Thanks
 
#36 · (Edited by Moderator)
You have to put the cwm-root-gtab2.zip file in the root directory of an external SD card in the slot. The recovery that you flash with Odin will not see the internal memory. Everything else you download to your PC.
 
Save
Reply Quote Like Like
Android OS Forum
posts
1.2M
members
138K
Since
2011
A forum community dedicated to Android phone owners and enthusiasts. Come join the discussion about applications, recovery, developments, styles, reviews, accessories, classifieds, and more for Unbuntu, Google Nexus, HTC, Motorola, Samsung or other Android models!
Full Forum Listing
Explore Our Forums
Droid 2 / R2D2 / Milestone 2 / Droid 2 Global Android Android Applications TWRP 2.X Ubuntu for Phones