Post Reply

[Solved] rooting SM-T210 under Linux?

26th January 2014, 02:06 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
10 posts
Join Date:Joined: Jan 2014
Hi,
I actually try to root my Galaxy Tab 3 according to this thread: http://forum.xda-developers.com/show....php?t=2433853

But I dont want to install Windows intentionally for this stuff so I try it under Arch Linux (64bit)... I downloaded the JOdin3CASUAL-linux-R991.tar.gz (the browserversion runs neither with jre7-openjdk nor jre from AUR) and installed Heimdall via AUR

But JOdin tells that the automatically generated pit is invalid (The PIT file was corrupt. We cannot continue without a PIT file.)

Code:
Entry Count: 20
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 22608
Unknown 4: 14657
Unknown 5: 14392
Unknown 6: 22616
Unknown 7: 0
Unknown 8: 0


--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 512
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PBL
Flash Filename: PBL.bin
FOTA Filename: 


--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: LT02.pit
FOTA Filename: 


--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 72
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 8142
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename: 


--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MRD
Flash Filename: ReliableData.bin
FOTA Filename: 


--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10240
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MRD_BK
Flash Filename: 
FOTA Filename: 


--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 12288
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: 
FOTA Filename: 


--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 20480
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename: loke_2nd.bin
FOTA Filename: 


--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 28672
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL
Flash Filename: loke_pxa988.bin
FOTA Filename: 


--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 36864
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename: 


--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 61440
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename: 


--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 77824
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: radio.img
FOTA Filename: 


--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 102400
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash Filename: boot.img
FOTA Filename: 


--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 126976
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename: 


--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 151552
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MISC
Flash Filename: 
FOTA Filename: 


--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 172032
Partition Block Count: 32768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: NVM
Flash Filename: NVM.img
FOTA Filename: 


--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 204800
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MEP
Flash Filename: 
FOTA Filename: 


--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 212992
Partition Block Count: 2945024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename: 


--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 3158016
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename: 


--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 3567616
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename: 


--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 3977216
Partition Block Count: 11284480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USER
Flash Filename: userdata.img
FOTA Filename: remained
Does anybody has experience with Heimdall under Linux?
Last edited by randallskii; 28th January 2014 at 10:15 AM. Reason: solved/update
27th January 2014, 06:04 PM   |  #2  
OP Junior Member
Thanks Meter: 0
 
10 posts
Join Date:Joined: Jan 2014
Okay..I didnt get JOdin running correctly (still getting corrupted pit file message), but I got my device rooted via heimdall frontend (thanks to zibrah3ed).
If other linux users are having trouble rooting their devices - you can try this:

1.) download T210.CWM.6.0.4.5.recovery.tar.zip and android-armeabi-universal-root-signed.zip from here
2.) copy android-armeabi-universal-root-signed.zip to internal or external sdcard of device
3.) decompress T210.CWM.6.0.4.5.recovery.tar.zip (should give you recovery.tar.md5)
4.) rename recovery.tar.md5 to recovery.tar.gz
5.) decompress recovery.tar.gz (now you should have a file named recovery.img)
6.) put device into download mode with "home+vol down+power" and connect it
7.) verify device is detected via terminal:
# heimdall detect
8.) download pit file from your device via terminal:
# heimdall download-pit --output smt210.pit
(file is saved at the current folder you are situated in the terminal)
9.) let device auto-reboot, then reenter download mode
10.) start heimdall-frontend (I did it with gksudo heimdall-frontend) and click "Detect" (@Utilities tab of Heimdall)
11.) click on Flash tab of Heimdall
12.) browse for the downloaded pit file (@Options PIT)
Make sure "Repartition" is NOT checked/selected
13.) click on "Add" (@Partitions (Files))
14.) change Partition Name to RECOVERY (@Partition Details)
15.) browse for the decompressed recovery.img (@File (recovery.img))
16.) uncheck "No Reboot" & "Resume"
17.) hit start
18.) the device will automatically reboot when finished...
19.) turn off the device and press "home+vol up+power", when the Samsung logo shows up release power button but keep pressing "vol up+home" until you enter CWM Recovery mode (takes little while)
20.) install zip android-armeabi-universal-root-signed.zip (the navigation is a littlebit weird, but well explained here)
21.) reboot device

After the reboot my PlayStore was broken (displaying "no connection" although I was able to surf on websites in the browser)
Doing a factory reset in CWM Recovery mode helped and I was able to install Superuser.

Would be cool if I get JOdin running because its easier to handle.. but I have no idea how.

Anyways I think this problem is more releated to JOdin thread so mods feel free to close this one.
6th February 2014, 06:31 AM   |  #3  
Senior Member
Flag @my home
Thanks Meter: 95
 
308 posts
Join Date:Joined: Aug 2013
More
Can you send me The pit-file, i need it for tab.
Can i usw this file for re partion With Odin ?

Thanks for your help.
20th February 2014, 11:16 AM   |  #4  
OP Junior Member
Thanks Meter: 0
 
10 posts
Join Date:Joined: Jan 2014
Quote:
Originally Posted by bierma32

Can you send me The pit-file, i need it for tab.
Can i usw this file for re partion With Odin ?

Thanks for your help.

sry forget to activate thread subscription

here's my pit file downloaded via: heimdall download-pit --output smt210.pit

you can verify that it is the same as from the first post (factory setting) with heimdall frontend
go to Utilities, @ Print PIT check [O] Local File, @ PIT File Browse for smt210.pit, then click on "Print"

regarding Odin: sry no idea, because I dont use Windows and therefore I dont have much experiance with Odin..but I think it should be possible as long as the PIT-files are standardised
Attached Files
File Type: 7z smt210.pit.7z - [Click for QR Code] (869 Bytes, 169 views)
Last edited by randallskii; 20th February 2014 at 11:21 AM. Reason: added pit as 7z because of the board's file-permissions
6th May 2014, 12:57 AM   |  #6  
Junior Member
Thanks Meter: 0
 
15 posts
Join Date:Joined: Jan 2011
Quote:
Originally Posted by randallskii

sry forget to activate thread subscription

here's my pit file downloaded via: heimdall download-pit --output smt210.pit

you can verify that it is the same as from the first post (factory setting) with heimdall frontend
go to Utilities, @ Print PIT check [O] Local File, @ PIT File Browse for smt210.pit, then click on "Print"

regarding Odin: sry no idea, because I dont use Windows and therefore I dont have much experiance with Odin..but I think it should be possible as long as the PIT-files are standardised

Can this pit file be use for the Sprint Galaxy tab 3 7.0?
6th May 2014, 10:11 AM   |  #7  
OP Junior Member
Thanks Meter: 0
 
10 posts
Join Date:Joined: Jan 2014
my PIT file comes from a branded device (german isp 1&1, of which a logo is shown when booting)

but I cant tell if that is problematic, because I dont have another device to test this

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Galaxy Tab 3 Q&A, Help & Troubleshooting by ThreadRank