Database Info

Clean way to install Cyanogenmod

I want to install Cyanogenmod on my i5801 running froyo. Looking for a simple & clean method.
After hours of surfing, I have reached these two tutorials:
android.gs / update-galaxy-3-i5801-apollo-cyanogenmod-7-2
newtechie . com / 2012 / 01 / how-to-install-cyanogenmod-7-on-samsung.html
Which one is the recommended way? During my search, I learnt of something called Clockworkmod. Is there any need to first have CWM on my phone? Are there any prerequisites (other than mentioned in the tutorials) that need to be taken care of.
During the learning process, I have already rooted the phone using Super One Click, v 1.7.
Please help.

Click in this link > http://forum.xda-developers.com/showthread.php?t=1372414.
This is the tutorial for how to install any ROM on our phone.

If you have already rooted your phone, flashing cm is not very complicated.
just follow simple steps
1.download the cm7 odin package
2. download odin package for i5800 with ops file
3. open odin ..choose ops file
4. click 'one package' option
5. select cm7 tar package.
6. start phone in download mode pressing power, home and vol down together.
7. connect usb cable ...odin will show yellow color in one port
8. start upload and wait until reboot
9. wipe data factory setting while still connected with usb and pc
10. wait until odin says 'pass' with yellow turning blue.
11. disconnect usb and use cm7.

Abhijeetsinghvsf said:
If you have already rooted your phone, flashing cm is not very complicated.
just follow simple steps
1.download the cm7 odin package
2. download odin package for i5800 with ops file
3. open odin ..choose ops file
4. click 'one package' option
5. select cm7 tar package.
6. start phone in download mode pressing power, home and vol down together.
7. connect usb cable ...odin will show yellow color in one port
8. start upload and wait until reboot
9. wipe data factory setting while still connected with usb and pc
10. wait until odin says 'pass' with yellow turning blue.
11. disconnect usb and use cm7.
Click to expand...
Click to collapse
I also read that I should first make a backup of my current rom using Clockworkmod. Is it a must? How to do that?

g3noob said:
I also read that I should first make a backup of my current rom using Clockworkmod. Is it a must? How to do that?
Click to expand...
Click to collapse
It's not a must but if anything does go to then it comes in handy because you can just restore the backup.
To get Cwm you can root your phone using superoneclick the flashing g3mod 2.5 kernel.
Press thanks if i helped.

Abhijeetsinghvsf said:
If you have already rooted your phone, flashing cm is not very complicated.
Click to expand...
Click to collapse
Root access is not relevant for flashing via Odin

MicroGeek said:
It's not a must but if anything does go to then it comes in handy because you can just restore the backup.
To get Cwm you can root your phone using superoneclick the flashing g3mod 2.5 kernel.
Press thanks if i helped.
Click to expand...
Click to collapse
I'm preparing myself to do CM7 flashing. I've already done single-click rooting using superoneclick, but my friend advised me not to use single click rooting which he says is bit unsafe. Instead he said that I should unroot the system and root it via the terminal method. Is my friend correct?

just flash a custom Rom and there is no need to mess about rooting your phone.
Sent from my GT-I5800 using xda app-developers app

Guys! Successfully installed Cyanogenmod 7.2 alpha 8. Great Experience... Thanks all!

simbawimba said:
just flash a custom Rom and there is no need to mess about rooting your phone.
Sent from my GT-I5800 using xda app-developers app
Click to expand...
Click to collapse
Still in doubt...
my cell is non rooted and want to install CyanogenMod 7.2 (Alpha8.3 - 13/08/2012) / Kyrillos_rom_v9.6
(http://forum.xda-developers.com/showthread.php?t=1101218)
http://forum.xda-developers.com/showthread.php?t=957123
Q1. do i need to root my phone,
If no, then can i just put the phone in download mode and update/flash it with above ROM
as described in (http://forum.xda-developers.com/showthread.php?t=1372414)
Q2. If i need to root my phone, then what tool should i use to root it (pls give one perfect sure shot tool name)
Q3. After rooting and installing CyanogenMod 7.2/Kyrillos_rom_v9.6; If i want move to I5801-DXJPC, will it be possible..?

[Q] AT&T SGH-I727 Odin Crashes at "Getting PIT for mapping..."

Hello
I have an issue trying to use KIES, ODIN, or Heimdall Suite trying to flash just about anything to an AT&T Galaxy S II Skyrocket - SGH-I727. This phone was my brother's and according to him he installed CW Recovery (do not currently have the version) successfully but when he tried to flash a new ROM the phone rebooted with the "Firmware upgrade encountered an issue..." screen. He is adamant that anytime he used ODIN he did not leave the option for PIT checked.
These are the steps I have tried to flash back to stock
1. Use KIES as recommended by the error on the screen. Installed the Samsung Galaxy S II Skyrocket drivers, phone is detected by windows device manager and I attempt to do an emergency recovery. The process gets all the way to the point of trying to flash the new firmware but hangs there. I let it run for over 48 hours and did not move a single percent.
2. Use ODIN to flash a Stock Recovery TAR. ODIN, of any version number but specifically 1.85, will crash with an 0xc0000005 error at "Getting PIT for mapping..." consistently. I have tried this across three different physical Windows 8 and 7 machines, Windows XP mode on one of them, and a myriad of different micro USB cables.
3. Use Heimdall Suite, versions 1.3.1 and 1.3.2, on both Windows platform and Ubuntu running in a virtual machine. The device is detected on both platforms. On windows the software will hang if I try to read the PIT. On Ubuntu it will "read" the PIT but the file produced is 0 bytes. If I try to flash the TAR file using Heimdall then when the phone reboots it hangs at the Samsung logo and I can put it into download mode without getting the "Firmware upgrade encountered an issue..." message. However, neither ODIN or Heimdall will do a successful flash.
From most of my searches and reading of posts it seems that if I can get into Download Mode then the phone is not hard bricked. It appears though there is some form of corruption in the PIT if that is possible, like a quasi-brick.
As a last ditch effort I wanted to take fate in my hands and do flash the PIT but I have not been able to find a PIT file for the SGH-I727.
Does anyone know if there is a PIT file for the SGH-I727 or have any other suggestions for how to get the phone back to stock? Or, does it look like even though I can hit download mode JTAG will be the only real solution?

Have you tried one of the Odin one clicks, it can be found here... http://www.androidaddicted.com/firm...lc4-ics-4-0-3-leaked-firmware-update-576.html
Sent from my SGH-I727 using Tapatalk 2

worias said:
Hello
I have an issue trying to use KIES, ODIN, or Heimdall Suite trying to flash just about anything to an AT&T Galaxy S II Skyrocket - SGH-I727. This phone was my brother's and according to him he installed CW Recovery (do not currently have the version) successfully but when he tried to flash a new ROM the phone rebooted with the "Firmware upgrade encountered an issue..." screen. He is adamant that anytime he used ODIN he did not leave the option for PIT checked.
These are the steps I have tried to flash back to stock
1. Use KIES as recommended by the error on the screen. Installed the Samsung Galaxy S II Skyrocket drivers, phone is detected by windows device manager and I attempt to do an emergency recovery. The process gets all the way to the point of trying to flash the new firmware but hangs there. I let it run for over 48 hours and did not move a single percent.
2. Use ODIN to flash a Stock Recovery TAR. ODIN, of any version number but specifically 1.85, will crash with an 0xc0000005 error at "Getting PIT for mapping..." consistently. I have tried this across three different physical Windows 8 and 7 machines, Windows XP mode on one of them, and a myriad of different micro USB cables.
3. Use Heimdall Suite, versions 1.3.1 and 1.3.2, on both Windows platform and Ubuntu running in a virtual machine. The device is detected on both platforms. On windows the software will hang if I try to read the PIT. On Ubuntu it will "read" the PIT but the file produced is 0 bytes. If I try to flash the TAR file using Heimdall then when the phone reboots it hangs at the Samsung logo and I can put it into download mode without getting the "Firmware upgrade encountered an issue..." message. However, neither ODIN or Heimdall will do a successful flash.
From most of my searches and reading of posts it seems that if I can get into Download Mode then the phone is not hard bricked. It appears though there is some form of corruption in the PIT if that is possible, like a quasi-brick.
As a last ditch effort I wanted to take fate in my hands and do flash the PIT but I have not been able to find a PIT file for the SGH-I727.
Does anyone know if there is a PIT file for the SGH-I727 or have any other suggestions for how to get the phone back to stock? Or, does it look like even though I can hit download mode JTAG will be the only real solution?
Click to expand...
Click to collapse
There is no pit for the skyrocket.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

xcrazydx said:
There is no pit for the skyrocket.
Click to expand...
Click to collapse
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.

cschmitt said:
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
Click to expand...
Click to collapse
cschmitt, this is exactly what I needed! I was able to flash the PIT file in ODIN without crashing. I then flashed the stock firmware using ODIN and the phone is now booting perfectly. All is well.

Great news! Glad you're back up and running.

worias said:
cschmitt, this is exactly what I needed! I was able to flash the PIT file in ODIN without crashing. I then flashed the stock firmware using ODIN and the phone is now booting perfectly. All is well.
Click to expand...
Click to collapse
Did you have another phone to extract it from? Or was that file cschmitt attached what you odined?
Sent from my SAMSUNG-SGH-I727 using xda premium

cschmitt said:
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
Click to expand...
Click to collapse
i dont/never used adb, can u post the commands(step by step) so i can put it in the 1 stop sticky
worias said:
cschmitt, this is exactly what I needed! I was able to flash the PIT file in ODIN without crashing. I then flashed the stock firmware using ODIN and the phone is now booting perfectly. All is well.
Click to expand...
Click to collapse
to confirm, u didnt use adb to flash the pit file, you used odin to flash the pit file and used the pit option in odin, then you picked pda option for the stock firmware, more details u give the better so i can add it to the sticky

cschmitt said:
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
Click to expand...
Click to collapse
Cool, thanks!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

@vincom, yes flashing the pit in Odin along with a stock rom in PDA is the safest method.

Yes please vinvom put it in your stickies, it'll help a lot of us.
Sent from my SGH-I727 using xda app-developers app

cschmitt said:
@vincom, yes flashing the pit in Odin along with a stock rom in PDA is the safest method.
Click to expand...
Click to collapse
so, to confirm, use the pit option, no reboot, then immediately flash stock files, or do then simultaneously
can u also give the adb commands for the pit, can adb also be used for the stock firmwares, which i dont think we can

cschmitt said:
@vincom, yes flashing the pit in Odin along with a stock rom in PDA is the safest method.
Click to expand...
Click to collapse
Was that file you posted the actual pit used in ODIN? It's the same for all our skyrockets/Rogers I727rs ?
Sent from my SAMSUNG-SGH-I727 using xda premium

stoopendis said:
Was that file you posted the actual pit used in ODIN? It's the same for all our skyrockets/Rogers I727rs ?
Click to expand...
Click to collapse
Yes, celox.pit (extracted from the zip) is the actual pit to flash in ODIN. It's from an SGH-I727 and should be the same for Rogers version. Not 100% sure if it's the same for TMO flavor.

vincom said:
so, to confirm, use the pit option, no reboot, then immediately flash stock files, or do then simultaneously
can u also give the adb commands for the pit, can adb also be used for the stock firmwares, which i dont think we can
Click to expand...
Click to collapse
k in going to use this thread to link from the sticky and also add it in the odin troubleshootibg section in restoring to stock
********************************************
when trying to flash stock firmwares and/or recoveries and it hangs at "Getting PIT for mapping" or getting pit errors in odin, download celox.zip and "unzip" the file, select the extracted "celox.pit" file in the pit option for odin, with all other options unchecked hit the start button in odin, once flashed you can then flash the stock firmware and/or recovery in odins pda section.
thanks cschmitt

Extract celox.pit from the zip and flash the pit file, do not attempt to flash the zip file directly.

cschmitt said:
Extract celox.pit from the zip and flash the pit file, do not attempt to flash the zip file directly.
Click to expand...
Click to collapse
k, i reedited the post

stoopendis said:
Did you have another phone to extract it from? Or was that file cschmitt attached what you odined?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I used the attachment from cschmitt, extracted the PIT file from the zip and then used ODIN to flash it. I was then able to flash a Skyrocket Stock ODIN tar to restore to GB and boot the phone. I have since been able to get it rooted, CWTouch on it, and have CM10 running on it well.
Thanks again everyone.

I did copy TWRP2.2.0 and stock firmware zip in SD card and hold volume up+down + power button to get recovery mode but I only see pictures of phone & monitor with yellow
triangle at center.( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again.)
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
I upgraded my samsung s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1) .
I just tried other laptop to use Odin & stock 4.0.4 to flash back Stock rom.and got getting mapping pit....I still can go to Download mode but I can't flash anything.
Please help . Thank you very much.

If I understand, you're trying to flash 4.0.4 with odin. And it's a md5 file, right? Keep trying it. Sometimes it takes more than one try.
And check the check sum of the stock rom file you downloaded it could be a bad download
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round

[Q] Galaxy Tab 2 7" P3110 trouble, now bricked?

Hello,
After rooting (flashing) my brand new Galaxy Tab 2 7" via the following link (will not show): androidauthority.com /galaxy-tab-2-7-0-p3110-root-clockworkmod-recovery-96473/, method Heimdall, with the files from this site, the device is stuck at the bootscreen. I did follow the instructions exactly. The ./su in the adb shell segfaults however, so i can't continue, and it won't startup either. So i guess now it's bricked. I read somewhere it has to do with the software version number that was incompatible.
Can i go back to the old firmware, or install another android 'distro' (that was my intent for the long run and the reason to root it first)?
I can still adb shell into it, but no root however.
I'm a newbie in the android world btw.

Hi,
Search for the latest Stock Firmware files of P3110 for your country and flash it with ODIN... Check the development thread and you'll find information on how to flash stock firmware with odin...procedure will be the same only files will differ...
To go into download mode, turn off your device, press vol. down, keep it pressed and with that press the power button...start odin on your computer and connect the tab to your computer and flash the file....
Zeroclick said:
Hello,
After rooting (flashing) my brand new Galaxy Tab 2 7" via the following link (will not show): androidauthority.com /galaxy-tab-2-7-0-p3110-root-clockworkmod-recovery-96473/, method Heimdall, with the files from this site, the device is stuck at the bootscreen. I did follow the instructions exactly. The ./su in the adb shell segfaults however, so i can't continue, and it won't startup either. So i guess now it's bricked. I read somewhere it has to do with the software version number that was incompatible.
Can i go back to the old firmware, or install another android 'distro' (that was my intent for the long run and the reason to root it first)?
I can still adb shell into it, but no root however.
I'm a newbie in the android world btw.
Click to expand...
Click to collapse

I'm downloading 4.1.1. from samsung-updates.com, since that was the latest version for my country (NL). I flash with Heimdall, since i don't have windows, or is there something special with Odin?
Now i'm going to flash it, is it possible to root it in the process? Else i have to flash it later again.
varundave said:
Hi,
Search for the latest Stock Firmware files of P3110 for your country and flash it with ODIN... Check the development thread and you'll find information on how to flash stock firmware with odin...procedure will be the same only files will differ...
To go into download mode, turn off your device, press vol. down, keep it pressed and with that press the power button...start odin on your computer and connect the tab to your computer and flash the file....
Click to expand...
Click to collapse

Zeroclick said:
I'm downloading 4.1.1. from samsung-updates.com, since that was the latest version for my country (NL). I flash with Heimdall, since i don't have windows, or is there something special with Odin?
Now i'm going to flash it, is it possible to root it in the process? Else i have to flash it later again.
Click to expand...
Click to collapse
Idk but I usually flash with odin

The file is 706MB. The boot-bjr.img file that i installed is only 5.6 MB. Can someone explain what is going on here? I don't feel comfortable with this and i cannot find any description of how the flashing actually works, what you are replacing by flashing, what format/partitioning the flash has e.t.c.
qazmed said:
Idk but I usually flash with odin
Click to expand...
Click to collapse

Just for the record, i was able to install cyanogenmod on it, by first installing clockworkmod recovery. Heimdall and adb is all you need if you're a linux user.

Don't worry its not a brick.
Or a hard brick at least.
Download the stock ROM from sammobile or samsung-updates. Doesn't matter which. Extract the zip. Flash the .md5 file with Heimdall or if that doesn't work rename it to .tar.
To root it properly follow my root tutorial but use Heimdall when I use Odin. http://www.youtube.com/watch?v=pAvze-VNzj8&feature=youtube_gdata_player
Sent from my GT-P3113 using Tapatalk HD

[Q]Unable to root my device from recovery

I Am unable to mount system or cache either and also i cant flash certain files from my CWM recovery I think it is because I forgot to root my device before flashing the CWM from stock recovery. Now I can't do nandroid backup or root the device either i need help. The data speed is too slow at my home I'll not be able to download stock rom (it would take days to download)... Is there any way??

smartananallavan said:
I Am unable to mount system or cache either and also i cant flash certain files from my CWM recovery I think it is because I forgot to root my device before flashing the CWM from stock recovery. Now I can't do nandroid backup or root the device either i need help. The data speed is too slow at my home I'll not be able to download stock rom (it would take days to download)... Is there any way??
Click to expand...
Click to collapse
Recovery Mode doesn't need root to function. Try the Universal GB Root package and tell me what happens, a bit more information would be helpful, like, if an error shows, or something like that...
EDIT: OH! I just realized what is happening! You are using CWM with a Stock ROM that you want to root, right? Well, CWM does NOT support .EFS file systems. It can't mount the /system/ partition to write on it. When you install a custom ROM with it, it re-formats the system partition to EXT4. So, you can't use both a Stock ROM and CWM. They do not support each other. You need to flash a custom ROM. Or use the Stock Recovery to flash the Root Zip.

another trouble.....
thanks i figured that out but also now there is another problem...please help me.
I downloaded the stock rom and it has only two files ( a .dll and an file HOME.tar) but i loaded the file as PDA in
odin and now there comes the problem.... the drivers are setup and the ID:COM section turns yellow and then in the
logs everything proceeds good and gets stuck at the setupconnection stage. I'll try to post the screen shot

smartananallavan said:
thanks i figured that out but also now there is another problem...please help me.
I downloaded the stock rom and it has only two files ( a .dll and an file HOME.tar) but i loaded the file as PDA in
odin and now there comes the problem.... the drivers are setup and the ID:COM section turns yellow and then in the
logs everything proceeds good and gets stuck at the setupconnection stage. I'll try to post the screen shot
Click to expand...
Click to collapse
Ok, i'll wait for the screenshot =)
Also, this is a first i have ever heard of this problem. If the drivers are OK, Odin is showing the COM Port, and the Setup begins, my only guess is that you got the wrong flash files... Are you sure you'r device is "s5670"? not some other model? Also, i recommend downloading official firmware from SamFirmware. But for now, i wait for screenie =)

smartananallavan said:
thanks i figured that out but also now there is another problem...please help me.
I downloaded the stock rom and it has only two files ( a .dll and an file HOME.tar) but i loaded the file as PDA in
odin and now there comes the problem.... the drivers are setup and the ID:COM section turns yellow and then in the
logs everything proceeds good and gets stuck at the setupconnection stage. I'll try to post the screen shot
Click to expand...
Click to collapse
Don't load it as PDA, instead load it as One Package(home.tar.md5 file)

my samsung doesnt open
i tried to install cyanogen 10.4.1 jelly bean to my galaxy fit but i didnt root it first i realized that later and it couldnt wipe and couldnt install the update. the problem is that it doesnt open any more. it stays at galaxy fit screen what can i do to restore it?

Stay Calm Bro
koukis32 said:
i tried to install cyanogen 10.4.1 jelly bean to my galaxy fit but i didnt root it first i realized that later and it couldnt wipe and couldnt install the update. the problem is that it doesnt open any more. it stays at galaxy fit screen what can i do to restore it?
Click to expand...
Click to collapse
Hi @koukis32
Dnt wry Bro ur cell is just fine please download the Firmware pages that you want to flash from the link below by entering your phone model number or i shall also paste link where in you can download the package directly also.
You can find the required ODIN Firmware Package as you wish for the ODIN tool
http://www.sammobile.com/firmwares/ and put in the Device Model Number and download it
or complete Firmware Package of Gingerbread 2.3.6 DDKT3 you can find the link below
http://hotfile.com/dl/146050815/b3b9...2_INU.zip.html in case this link doesn't work please download the Packages from above link as I can't check it from my office so dntmnd
For ODIN Flashing Tool:
http://www.downloads.techdiscussion....ting-software/
and Procedure to Flash is:
- Shutdown Galaxy Fit and restart it in Recovery Mode. For that hold the volume down key + Home key and power key. Hold it for some seconds and leave it. The device will boot in recovery mode. When the yellow triangle, connect cell phone and a computer with a USB cable.
- Launch ODIN on your system. In that look under ID:COM section. The section will turn to yellow once the device is connected and detected.
- Now click on OPS. It will ask you to browse the downloaded firmware package. Browse to GIO_1.0.ops. Once it is selected click on One Package and choose S5670DDKT3_S5670ODDKT2_S5670DDKT2_HOME.tar.md5.
- Now click on Start. The update process has started and it will take few minutes to complete.
- Once it is done, the device will reboot itself. Later on you can go in Settings and checkout the firmware version.
And considering still you still in Galaxy Fit Page then go take a break and relax and follow the instructions in the link which I have shared you phone will come back to life.
http://www.androidauthority.com/how...xy-fit-s5670-android-2-3-4-gingerbread-35369/
follow the picture carefully.
:good::fingers-crossed::fingers-crossed::fingers-crossed:

AXAz0r said:
Ok, i'll wait for the screenshot =)
Also, this is a first i have ever heard of this problem. If the drivers are OK, Odin is showing the COM Port, and the Setup begins, my only guess is that you got the wrong flash files... Are you sure you'r device is "s5670"? not some other model? Also, i recommend downloading official firmware from SamFirmware. But for now, i wait for screenie =)
Click to expand...
Click to collapse
thaks for helping sorry for the long Delay. solved the problem!!!! just downloaded a stock deodexed rom.zip and flashed...... booted up fine

Root SM-T210/R using Heimdall

I took a little time playing around with Heimdall. It's....... different.
I have taken the time to simplify some of the steps for everyone, and built the required file myself.
I used TWRP 2.8.0.0 "img" file from their website. All development credit go to TeamWin, I've just converted it to the proper file format for Heimdall.
edit: The file use is actually a port to the Tab 3 by gr8nole. I was wrong about a couple of things. So, credit goes to TeamWin for original dev, and to gr8nole for porting it to the Tab 3 for us
Before reading farther, please remember:
ALL FLASHING IS DONE AT ONE's OWN RISK, I'M NOT RESPONSIBLE.
Please take adequate precautions to be able to recover your device from a soft brick.
This method is for KitKat users.
I used the Pit mapping for the T210. The recovery partition is "mmcblk0p10." I checked the partition info on my T210R using Partition Table by Lakshman. The T210R also has its Recovery partition on "mmcblk0p10," so I expect it to work no problem. And TWRP Odin flashables tend to be compatible with several 7.0 variants.
1. Open Heimdall. Reboot your device into download mode (power+volume down+home, then volume up).
2. Attach tablet to computer.
3. Select "Load Package" tab if it isn't already.
4. Click the "Browse" button under "Heimdall Firmware Package."
5. Select the ".tar.gz" file attached to this thread.
6. Click "Load/Customize." This will jump you to the "Flash" Tab.
7. Make sure that the "Repartition" check-box is unselected.
8. Click "Flash."
9. After flashing, reboot into your new recovery and install SuperSU and BusyBox.
As of this point, I have not been able to test this. I hope it goes well for anyone who tries it
Update:
As of now, I have been able to test this file on my own T210R. I already had this version of TWRP installed, so can't confirm actual update, but Heimdall said it flashed, and it didn't brick it, so I'd say good to go! (Take appropriate precautions anyways, because you never know what will happen.)

Worked well, thanks

Greaper88 said:
I took a little time playing around with Heimdall. It's....... different.
I have taken the time to simplify some of the steps for everyone, and built the required file myself.
I used TWRP 2.8.0.0 "img" file from their website. All development credit go to TeamWin, I've just converted it to the proper file format for Heimdall.
Before reading farther, please remember:
ALL FLASHING IS DONE AT ONE's OWN RISK, I'M NOT RESPONSIBLE.
Please take adequate precautions to be able to recover your device from a soft brick.
I used the Pit mapping for the T210. The recovery partition is "mmcblk0p10." I checked the partition info on my T210R using Partition Table by Lakshman. The T210R also has its Recovery partition on "mmcblk0p10," so I expect it to work no problem. And TWRP Odin flashables tend to be compatible with several 7.0 variants.
1. Open Heimdall. Reboot your device into download mode (power+volume down+home, then volume up).
2. Attach tablet to computer.
3. Select "Load Package" tab if it isn't already.
4. Click the "Browse" button under "Heimdall Firmware Package."
5. Select the ".tar.gz" file attached to this thread.
6. Click "Load/Customize." This will jump you to the "Flash" Tab.
7. Make sure that the "Repartition" check-box is unselected.
8. Click "Flash."
9. After flashing, reboot into your new recovery and install SuperSU and BusyBox.
As of this point, I have not been able to test this. I hope it goes well for anyone who tries it
Update:
As of now, I have been able to test this file on my own T210R. I already had this version of TWRP installed, so can't confirm actual update, but Heimdall said it flashed, and it didn't brick it, so I'd say good to go! (Take appropriate precautions anyways, because you never know what will happen.)
Click to expand...
Click to collapse
You say you took TWRP from TeamWin's website? Can you show me that, because I'm pretty sure they don't support this device.

gr8nole said:
You say you took TWRP from TeamWin's website? Can you show me that, because I'm pretty sure they don't support this device.
Click to expand...
Click to collapse
Maybe not their official website... oops.
The file I used you've uploaded... my mistake, thought you were part of their project.

Well the TWRP image file worked well enough for me... Either way...
I think this is the main way to root the T210(R) if updated to KitKat. Since it is quite possible that it's the last update it's ever going to see, I'd say it's good time to root it now and put Xposed on it for good measure.

xaueious said:
Well the TWRP image file worked well enough for me... Either way...
I think this is the main way to root the T210(R) if updated to KitKat. Since it is quite possible that it's the last update it's ever going to see, I'd say it's good time to root it now and put Xposed on it for good measure.
Click to expand...
Click to collapse
This version of TWRP is still compatible with JellyBean. I restored and booted my stock OS using this flash. And this is the same method that I had used to root before the update. (using Odin rather than Heimdall though.)

@Greaper88 did you test other files to confirm that functionality is working well (just curious) ?
Heimdall is interesting tool but i haven't tested it myself.

mkaymuzik said:
@Greaper88 did you test other files to confirm that functionality is working well (just curious) ?
Heimdall is interesting tool but i haven't tested it myself.
Click to expand...
Click to collapse
Do you mean other Heimdall installer files?
I've not tested other files as I've only messed with my Tab 3, and any flash files have to be built from a raw ".img" (image) file and the device's PIT (Partition Information Table). This presents challenges that I haven't tried to overcome.
I saw a request somewhere in another thread for a walkthrough on rooting the Tab 3 with Heimdall, and I figured out and posted this since it was only the recovery, and that much was actually somewhat easy.
My idea was, if you get custom recovery, you can then install your choice of ROM. Although I don't know if there is a TWRP flashable stock KK ROM yet...
I'm confident that the method in this thread for mentioned devices works based on my own flash and on "xaueious'" posts.
To port this method to other devices, one just needs the device's PIT and the recovery image file, "recovery.img" for example in order to build a flash file. The process is actually easy once you know how.
Full ROMs would be more difficult I think because there are other files besides ".img" files that have to be written to the flash, and a XML file has to be built as well to handle all of that. I haven't had time to mess with all of that...

Greaper88 said:
Do you mean other Heimdall installer files?
I've not tested other files as I've only messed with my Tab 3, and any flash files have to be built from a raw ".img" (image) file and the device's PIT (Partition Information Table). This presents challenges that I haven't tried to overcome.
I saw a request somewhere in another thread for a walkthrough on rooting the Tab 3 with Heimdall, and I figured out and posted this since it was only the recovery, and that much was actually somewhat easy.
My idea was, if you get custom recovery, you can then install your choice of ROM. Although I don't know if there is a TWRP flashable stock KK ROM yet...
I'm confident that the method in this thread for mentioned devices works based on my own flash and on "xaueious'" posts.
To port this method to other devices, one just needs the device's PIT and the recovery image file, "recovery.img" for example in order to build a flash file. The process is actually easy once you know how.
Full ROMs would be more difficult I think because there are other files besides ".img" files that have to be written to the flash, and a XML file has to be built as well to handle all of that. I haven't had time to mess with all of that...
Click to expand...
Click to collapse
Thx for the info mate. Going test this out.

I'm lost, I was working on my hubby's tablet and somehow the backup I made got wiped when I tried to Samsung Galaxy Tab 3 7.0 WiFi SM-T210/T210R Performance Upgrade MOD. I'm assuming that it doesn't work under KitKat as I was running TranchidaKat v2.2 [4.4.2 SM-T210/R Rom. Anyway whatever I did no matter what I wipe I keep getting one error from Odin, ""can't mount ES' I'd sure appreciate a hand on this thing if your around. I've been trying to run Heimdall but it always fails in Odin. What really confused me on your directions is you saying to open the package and select Load the Package. I'm not sure exactly what that means but I have Odin 3.07 through 3.10 and I don't see anything like that, could you clarify. I can load the regular 2.8 TWRP using the img file that has nothing to do with Heimdall so I can get into recovery but that's where I'm stuck. Any thoughts???
Krissy

Odin is leaked Samsung Software. Heimdall is an open source substitute, and is not related to Odin. Heimdall requires the TWRP file posted in the OP in this thread to work, but it will not work in Odin.
If you have a custom recovery installed that you can boot into, check out:
http://forum.xda-developers.com/gal...-stock-sm-t210r-4-1-2-jellybean-twrp-t2951850
If you've lost your backup files, then these ones might work for you unless the device flash has been overly corrupted.
If that doesn't work, check out:
http://forum.xda-developers.com/galaxy-tab-3/general/tab-3-7-0-sm-t210-r-stock-4-4-2-kitkat-t2930075
That's intended to be flashed directly from Odin, and will make the device stock KitKat.
I then like to use the Werewolf Kernel, since it overclocks the Tablet and improves overall speed that way.
Other thoughts: have you tried another USB cable/port? I've had similar errors simply because Odin didn't like my USB cable, or the USB port I was connected to.