[Official Firmware] T311 (works for ODIN recovery brick fix)

[Official Firmware] T311 (works for ODIN recovery brick fix) - Galaxy Tab 3 General

Hey all,
I had an adventure today. I soft bricked my tablet phone (SM-T311 unlocked). On a later post I will give instructions on how I successfully rooted this device and installed ROMs, but here I will tell you what I did wrong and how to fix it.
First some background. After installing 2 ROMs and downloading a bunch of apps for rooted phones I felt pretty confident in myself. I figured I'd try one more ROM to see if it might have better phone functionality. I read through the instructions on the developer's page and proceeded. I usually go very slow and proceed one step at a time, but this time I quickly read through the 5-6 steps and thought, ok, I got this. Well, I got one of the steps reversed and soft bricked my phone. What a pain!! I ended up missing work to get my phone fixed. After researching and trying different stuff, I found what worked. Here's what I did to unbrick my soft-bricked tablet.
Unfortunately I cannot post attachments yet, but when I can I will attached the tar.md5 stock firmware file for anyone who needs it. If you have an emergency you can send me a message with you E-mail, or post it below, and I'll send it to you.
INSTRUCTIONS:
1 - Download ODIN (I used version 3.07)
2 - Download original firmware from sammobile dot com / firmware (I do not mind E-mailing it to anyone who needs this until I can get it posted)
a. Sign up for a free account
b. On firmware page, scroll down midway and search for T311 (you can find just about any Samsung firmware here)
c. My tablet is unlocked and not tied to a carrier so I chose "unknown" source
d. It will take an hour to download because it's a "free" account. Make sure your phone is charging in the meantime. When finished downloaded proceed.
3 - Get your phone into download mode (hold down Power+Down+Home).
4 - Plug your phone into your computer
5 - Run Odin as administrator, make sure "auto reboot" and "reset time" boxes are checked, will say "Added!" in Message box when it reads your phone. NOTE - if it is not reading your phone you need to install Samsung drivers, you can find them on XDA or Samsung website. I assume you are, however, able to connect to your computer if you got as far as bricking your tablet.
6 - Put the downloaded file into the Odin folder (though I really don't think it matters where you put it, but that's what everyone says to do)
7 - Push PDA button and attached tar.md5 firmware file
8 - Push run and let it go its course (appx 20 minutes)
Your phone will restart and work like new.
UPDATE//
..removed my ROM observations, was confusing to some...More importantly:
If you do a fresh install with firmware and a PIT file to complete a nand erase and then your phone gets stuck on the Samsung logo after it reboots, please re-root and then install CWM 6.0.4.5. I cleared caches on CWM and rebooted. Then my phone worked new.
My lessons learned after all this... I'm just sticking to a simple root for access to my favorite apps, and not doing anything else beyond that.
For anyone who messed your T311 up and need to restore it to new, hopefully this helped!!

Wrong forum... This one is for thr 7" one, not the 8" version...
Sent from my XT1052 using XDA Free mobile app

Related

Samsung Galaxy Relay 4G Information Portal

I'm going to start collecting the various little tid-bits of information that we have scattered across the threads here to hopefully compensate without having a dedicated forum. Eventually I'll add some other guides and such from personal experience, if you know of any Relay related threads or other information located on the interwebs, please drop a link here!
Standard Disclaimer: I am not responsible for what you do to your phone. The information contained in this thread is here to help you do [anything] correctly. If you follow the instructions listed there-in you will be fine, and ask questions if you don't understand something. I am not responsible for what you do with and/or to your phone. If you are unsure about a procedure's outcome, do not proceed with the procedure.
(1)
How to Get Into Download Mode:
1. Hold Power, Vol Down, and Home button simultaneously
2. When "Samsung" appears on the screen let go of the power button but keep the other two pressed down
3. Voila!
Click to expand...
Click to collapse
ROMS:
[CM9][ALPHA]Galaxy S Relay 4G [12/8]
(Use the updated link below instead.) Stock + Odin Flash (+ Rooted System Img File)(Simplified Instructions)
Updated Stock ROM (Has LH1 flash-able via ODIN) Post + tested Tethering Fix(1)
How I reverted my phone to stock + root.
Update from LH1 to LMA2 On Stock ROM w/ preserved root (doesn't remove if you have root, but doesn't give you root) (Untested)
Update from LJ1 to LMA2 on Stock ROM w/ preserved root (doesn't remove if you have root, but doesn't give you root) (Untested)
Root:
[root]\{cm9} samsung galaxy relay 4g (updated 11/19)
General Discussion:
Galaxy S Relay 4G Development Thread
Miscellaneous Information:
Keyboard Customization:
Dillalade's Explanation on How To Set Custom Key Mapping(1)
jarrodlombardo's Key Mapping (Follow Dillalades's guide first)
orange808's Key Mapping
Unsorted, Need to Organize and Determine Relevance (If still applicable or OLD information) or Flesh out supporting information:
nopty's Hiemdal Method (Need to use Heimdal 1.41RC1 or Higher from This Post) (gee ones building heimdal for ubuntu 12.04)
AndriodForums Relay Forum
Sim Unlocking (Need to Verify - Unknown Method) (Sorta Verified)
Nardholio's Links to Create an Odin Flashable Image
NV Dump Backup (Important in case of corrupted IMEI)
Nardholio's Flash Counter Information
gee one dive's into nard's stock rooted img in response to Qualcomm secure boot
nopty's CWM recovery post (10-11-201) Odin Flashable of nopty's CWM Recovery
kornyone's introduction
How to change/remove startup/shutdown sounds
dillalade has issue with 64gb card w/ resolution to issue
fantomex's Andriod WPA2 PSK Authentication issue and resolution
Skinomi Skins for the Relay
gee one fixes his bootloop
gee one's list of bloatware Bloatware gee one was able to remove
Sim Unlocking for those who purchased Retail (no contract)
dillalade's guide to getting Google Now to work on the stock ICS Rom
Nardholio's Untested Tethering Fix
T-mobiles KIES LH1 Update Support Page
gee one investigates the efs partition on the relay Nardholio's response
CWM-Only Flash-able LJ1 Modem
Some changes from stock LH1 to LJ1

Reserved

Reserved 2

Just in Case

how about a link to the original factory rom to restore back to before CM9 ?

Kaczman said:
how about a link to the original factory rom to restore back to before CM9 ?
Click to expand...
Click to collapse
I found one that might work for you, update the OP with the info.
I've got to flash my relay to stock and when I do I'll create a small guide. For now I found an older flash that could be used then KIES could update this ROM to the current LH1 (Need to verify build number).
I need a stock rooted rom, while traveling through the mountains the switching in CM9 isn't working correctly (phone constantly looses service when switching from 4g>3g>Edge frequently).

Here's another sim unlock. I can verify this one as working since I am now using my phone with Solavei. I purchased my phone directly from t-mobile (no contract). I used an AT&T sim to do this method.
http://forum.xda-developers.com/showpost.php?p=36400199&postcount=783
Sent from my SGH-T699 using Tapatalk

Spoxy said:
Here's another sim unlock. I can verify this one as working since I am now using my phone with Solavei. I purchased my phone directly from t-mobile (no contract). I used an AT&T sim to do this method.
http://forum.xda-developers.com/showpost.php?p=36400199&postcount=783
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
Thank you!
Update OP. It's still in the unorganized section, but it's there!

Thank you, is a very useful guide ! :good:

You should post your first post from this thread in the request thread to show everything going on. Should work better than just posting "Samsung Relay, please"

That's the plan after I get it organized. I'm also going to follow the instructions given by kinfauns.
It's a start.

Never really notice that many steps when you go through it quickly, but this is the process that I used to revert my CM9 + CWM recovery to Stock rom + Stock Recovery. I don't know if it was supposed to happen that way, but it did. After flashing the stock PDA file (via odin) I was able to flash the CWM recovery again while adding root to the stock rom.
All of the items talking about (roms, odin, root, ect) except a program to unzip the files can be found in links in the thread in my signature. For reference, I use 7zip and just rightclick>7zip>extract to folder.
How to go Back to stock w/root from CM9:
Download stock rom (newest is the LJ1 tar.rar).
Download Odin
Unzip LJ1 into it's own folder. Navigate to where you unzipped the file.
Rename unzipped file to remove .md5 so it ends in ".tar" instead of ".tar.md5"
Unzip Odin (into it's own folder, navigate to the folder)
Put phone in download mode (Instructions are quoted in the OP of the thread in my sig)
Start Odin (assuming that you have already plugged the usb cable into your computer)
Connect phone (that's in download mode) to computer via USB cable.
ODIN Will have blue "Added!" box after it's recognized the phone (2nd box from the top left)
In ODIN, click the "PDA" Box and select the .tar for LJ1 (the file you unzipped and renamed)
Uncheck the "auto-restart" radiobox under "Added!". Then Click Start.
Wait for odin to finish. Do not touch your phone or click any buttons in the odin program. After It's done, reboot the phone.
Go into recovery mode on the phone (Vol Up Instead of Vol Down)
Wipe SDCard and cache
Reboot phone. It may take a few minutes to pass the samsung screen. The phone will vibrate briefly as is finishes booting
Sign into the phone (google, facebook, ect...this is probably a skipable step).
Turn off phone. Reboot into download mode (Vol Down)
Download nopty's CWM recovery
Unzip file (into it's own folder, navigate to it), removing the .md5 like the file above
Connect phone to computer, after ODIN recognizes ("Added!") it click the PDA button
Navigate to the unzipped and renamed (".tar") CWM file and select it.
Unceck "Auto-Reboot". Click start
Wait to finish, then power off and reboot phone
After phone has re-booted connect to computer
After connected to computer, transfer SuperSU zip(CWM Flashable) to SD card (You'll need to download this too, can be found in the Updated Stock Roms link)
After that's transferred, reboot phone into recovery mode. (Vol Up)
Use CWM to flash the SuperSU zip
Reboot phone
Congrats, you now have a stock rooted phone!
Just the basic frame for the guide, will update with links and what little troubleshooting I know and add guide to OP after it's finished.

Working with you guys is awesome.
Anyways, you guys know the drill.
New Device Request Forum
I may be naive, but I would like to equivocate a thanks with a "signed" on the post above.
PM'd kinfauns, lets hope that he can help us get to the right people!

thanks
thanks

So, has anyone else gotte the software update notification and felt brave enough to run it? I don't want to have what happened with the G2 with their first update and lose root.
Also, the damn notification icon won't go away despite postponing the update.

zakiancel said:
thanks
Click to expand...
Click to collapse
your welcome
mikeybot said:
So, has anyone else gotte the software update notification and felt brave enough to run it? I don't want to have what happened with the G2 with their first update and lose root.
Also, the damn notification icon won't go away despite postponing the update.
Click to expand...
Click to collapse
Not yet for me. I'm playing around with a stock rooted (debloated) rom that gee one made right now, I didn't get the OTA update message though. If you do "update" you should still be able to flash CWM and enable root/superuser again. Keep up updated!

Help
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?

tany.jags said:
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
Click to expand...
Click to collapse
Broken compass?
I remember seeing a few posts about it too, but I didn't flag them unfortunately. Post the question in the Development thread and we may be able to get you an answer quicker :good:.

tany.jags said:
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
Click to expand...
Click to collapse
Broken? No, but on occasion, it does momentarily glitch up, but once you start moving it clears itself up. Nothing like what would happen with the G2. (I do also have GPS Status installed as well)

I did run the update after taking a look through the zips and deciding to take the plunge and see; and it does reflash the recovery, and while I do have Odin, I have as yet been unable to flash any CWM again. There are no errors, it just doesn't work. I am as yet hopeful though and will report my progress. I didn't see anywhere in the update where it updated the bootloader, so flashing should still work.

How to root your samsung galaxy s3 (easily)

**** UPDATED 7-24-13 *****
Please read the tutorial now as I have added a new section on how to unlock the bootloader for your Verizon Samsung Galaxy S3. If you are not using a verizon SGS3
specifically model SCH-i535 then you do not have to worry about unlocking your bootloader as it comes unlocked by default. If you are using a verizon samsung galaxy s3 model sch-i535 and you do not fully unlock your bootloader you could run into problems when using certain root apps such as "mobile odin pro" or you could run into big problems when trying to flash custom roms such as cyanogenmod roms.
In this update I am adding one final step at the end of the root process to fully unlock the boot loader for the verizon samsung galaxy s3. There will be two ways to unlock the bootloader. One way will be to flash a final bootchain file with Odin, and the other will be to use an app to unlock the bootloader. Depending on what version of android you are using and your phones baseband version you will either need to use odin or you could use the application for any android version such as 4.1.1 or 4.1.2 and you can use the application for any baseband version your phone might be. I will leave the choice up to you, but I will show how to do it both ways.
Samsung users, don't forget if you plan on flashing a custom rom that with Samsung phones you could get the ugly yellow triangle warning. To get rid of this yellow triangle you can either go to google play store and get "yellow triangle away" app or go to this forum on this great xda developers site: http://forum.xda-developers.com/showthread.php?t=1494114
**NOTE** for those of you who would like to see a video of how to root your phone using these exact steps you can go to here: http://www.youtube.com/watch?v=K4b9hcWHrW8&feature=share&list=FL8Y3FM4mtznp0GQbwkkwaSg
A member on this thread gave me that link and it is a video by phone rebel and show you how to root your verizon SGS3 using the same steps i have outlined in this tutorial. Thank you so much for providing that link to my attention, I am sure it will help many users here!
Hello everyone,
Well this is one of my first tutorials for this forum on how to root your Verizon Samsung Galaxy S3.
I just recently got my Verizon Samsung Galaxy S3 and all of the tutorials I found were quite complicated and not very detailed so I thought that
I would write this tutorial and maybe it might help others out there....
Since the Galaxy S4 is getting ready to come out, the price has dropped considerably for the S3 and i believe more and more people will be getting this phone and wanting to root it.
Oh, and if you want an alternative guide you can use this very excellent tutorial from another post on this amazing forum:
http://forum.xda-developers.com/showthread.php?t=2046439
Here is the specs for the phone I am using and the step by step process I used to root it.
Verizon Samsung Galaxy SIII model I535 running Android 4.1.2
Okay step 1 you are going to need some files...
First thing you are going to need is the Samsung Drivers so you can connect your phone to your computer and your computer can recognize it.
All of the files you are going to need I am just going to reference the link from the other tutorial that I posted above, no sense in redoing work
that has already been done especially if it has been done well!
1. You can get the samsung driver files here: http://forum.xda-developers.com/showthread.php?t=2046439
click on the link that says samsung drivers
2. You are going to need Odin you can get it from the same link, click on the Odin Link
3. You are going to need the VRALEC BOOTCHAIN you can get it from the link I posted in step 1 make sure you get this file it is very
important.
Since I am using a Verizon Samsung Galaxy S3 the bootloader comes by default locked so we need this file to unlock the bootloader
so we can root the phone. If we were using any other phone besides Verizon we would not have to worry about this but since I have
Verizon I have to do this. IMPORTANT: if you are not using a VERIZON PHONE DO NOT download this file or use it in the step
process you do not need it.
4. Next you are going to need the exploit so that you can root your phone and you can grab that from a different website, here is the address:
http://autoroot.chainfire.eu/
This is the CF-AUTOROOT file and this is what roots your phone. If you have the same phone as me scroll down to the SCH-I535 link and
download that file.
Okay now that we have all of that downloaded lets get things moving...
First thing we are going to need to do is install the Samsung USB drivers, so do that.
After the drivers are installed plug in your phone and make sure that it connects to your computer correctly, after it connects disconnect
your phone from your computer.
Next thing we are going to need to do is extract the ODIN zip file and install the Odin executable.
Now we need to get to the critical stuff...
Step 1. Make sure that [USB Debugging] is enabled in your phone, if it is not go to Settings -> Developer Options and enable it.
Step 2. Put your phone in DOWNLOAD Mode. You do that by pressing Volume Down + Home + Power button and hold it down till you see
a warning screen. When you see the warning screen hit Volume Up to allow Download mode.
Step 3. Now that your phone is in Download Mode you are going to connect your phone to your computer with ODIN RUNNING if
everything connects correctly you will see ODIN highlight yellow (older versions of ODIN) or highlight blue (newer ODIN versions)
Step 4. Now this is where previous tutorials kind of messed up in my opinion (just my opinion). Now that your phone is in download mode
you need to only have the "auto boot" option selected in ODIN and click on the bootloader button and select the VRALEC file
you downloaded earlier. Every tutorial i read said to use this file with the PDA button/option but you need to use it with the bootloader
button/option in ODIN. Now that you have the VRALEC file selected under bootloader in ODIN select START. This will reboot your
phone and if everything goes correctly your phone's bootloader will be unlocked.
After reboot make sure to disconnect your phone from your computer.
Step 5. After your phone reboots from step 4 turn off your phone and then boot it back into DOWNLOAD mode. Vol Down + Home + Power
Step 6. Now that your phone is in Download Mode again (Reconnect your phone to your computer) and make sure ODIN is still running
Step 7. With your phone connected go to the PDA option/button and when you select it choose the CF-AUTOROOT file you downloaded earlier
Step 8. With your PDA option selected hit start. When this happens your phone will reboot and your will see a CUSTOM lock icon on your
screen don't worry it is okay. Now you will see some new text on your phone and if everything is working you will see things like
"Android is UPDATING"
Your phone is now rooted! but you are not done...
This is where all of the other tutorials I found also fell short...
Your phone is rooted but it will not work correctly without SuperSU
Step 9. Go to the Google Play Store and Download SuperSU. When the download is complete run SuperSU and now your phone is fully
rooted. You can test it by downloading Android Terminal and running the terminal and typing "su" or by downloading a root required
app Titanium Backup.
*****UPDATED STEP*****
IMPORTANT NOTE: i want to point that this step is completely optional. You do not have to unlock your bootloader but i would recommend it. If you just want to use a stock rom and have your phone rooted then you can ignore this last step. But...if you want to flash custom rom's or do any kind of serious customize your phone, then you will need to have your phones bootloader unlocked. Plus with the application I am going to show you further down this tutorial, it is so easy to unlock your bootloader, you might as well go for it.
Step 10. Okay now from the link that I gave you above: http://forum.xda-developers.com/showthread.php?t=2046439 you are going to need to download another bootchain file to fully unlock your verizon samsung galaxy s3 model sch-i535 phone.Go into your phone and under settings go into "about phone' and look at the section "baseband version". Now depending on what version of android you are using will determine your baseband version. On my Verizon SGS3 running 4.1.2 my baseband version is I535VRBMB1 the important part is -> "VRBMB1" now go to site i provided in this step and download the bootchain for your specific phone.
Since my phones baseband version is "VRBMB1" i will download that bootchain file obviously. VRBMB1 is for android 4.1.2
The other boothchain files are "VRBLK3" for android 4.1.1 and "VRBMD3" for android 4.1.2
Now take that bootchain file that you downloaded and load up Odin again. Connect your phone to your computer (MAKE SURE YOUR PHONE IS IN DOWNLOAD MODE -> VOL DOWN + HOME + POWER) and wait for Odin show a connection. Odin will show a blue light on newer Odin versions and a yellow light on older Odin versions.
When the connection is made hit the "bootloader" button and select the proper bootchain file for your specific phone. Before you hit start make sure that only "Auto Reboot" is selected on the left hand side.
Now go ahead and hit start and if all goes well your phones bootloader should be unlocked. You can tell that your phones bootloader is unlocked two ways.
One, when your phone reboots the Samsung Logo in white bold/block writing will disappear within 1-2 seconds. It will go by very fast.
Two, the custom lock icon that showed up after you ran the CF-AUTOROOT exploit will now disappear, if for any reason if you still see this logo then your phones bootloader is still locked and you can either try to flash the bootchain file again or use the application I am about to tell you about.
For my phone flashing this bootchain file worked fine, but for my brother's phone he has a verizon samsung galaxy s3 model sch-i535 this did not work and I had to use an application to unlock his bootloader.
****UPDATE UNLOCKING THE BOOTLOADER WITH EZ-UNLOCK*****
Okay so my brother who has a verizon samsung galaxy s3 model sch-i535 asked me to root his phone just the other day. I rooted his phone following all the same steps I have written above with no problems. His phone rooted perfectly, however his bootloader would not unlock. I believe that his bootloader would not unlock because he had an updated version. While his android version was the same as mine 4.1.2 he had a different baseband version.
His baseband version was "I535VRBMF1" the important part -> "VRBMF1"
Now i have been told that you can use the bootchain file VRBMB1 to unlock the bootloader for verizon SGS3 running android 4.1.2 baseband version "VRBMF1" but when i tried it, the bootloader staid locked. So i had to use an application to unlock his bootloader.
The application i used was "EZ-Unlock" which you can get here: http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
Now this application is SO EASY to use it is amazing. Just download the file, the author recommend version 1.2 as the most stable and that is version i used. To download this file make sure you have the option "Unknown Sources" check in your Settings -> Security menu.
Okay to unlock your bootloader with EZ-Unlock follow these easy steps:
Step 10A. Download EZ-Unlock version 1.2 from the link above.
Step 10B. Install the application and open it.
Step 10C. Once open click on the giant "Unlock" button. If all goes well you will hear "That was easy" from the application.
Once you have hit the unlock button on EZ-Unlock reboot your phone to see if the Samsung in bold/block white letters disappears within 1-2 seconds, and make sure the custom lock icon has disappeared.
Now the application EZ-Unlock is designed specifically for verizon samsung galaxy s3 phones, it does not matter what baseband version you use or android version you use. So this is a very appealing and easy way to unlock your bootloader. If you don't feel like flashing a bootchain file with Odin or if you are not sure what bootchain file you should use then using this application. NOTE: you do need root access to run this application.
And that is it! Your phones bootloader should be unlocked either with Odin or EZ-Unlock the choice is all up to you!
***LAST THOUGHT ON INSTALLING CUSTOM RECOVERY***
This rooting method does not install and kind of custom recovery manager on to your phone. If you want to install a custom recovery manager such as "ClockworkMod Recovery" you can do that very easily once your phone is rooted. Once your phone is rooted go to the google play store and download "Rom Manager". Once Rom Manager is installed open it up and give it root access with SuperSU. Once that is done go into the option to flash a recovery manager and follow the steps and the application Rom Manager will take care of that for you!.
Congrats on rooting your phone! I hope this tutorial has helped you and I want to thank all of the system administrators of this forum and all of
the great guys and gals that contribute to this place. You guys/gals are what makes the open source community great!
I thank you all...
Hope it helped!
-droidshadow

Thanks might have to do this on my wife's phone
Sent from my SCH-I535 using xda premium

kgirlx said:
Thanks might have to do this on my wife's phone
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I think that the easiest way to root any Samsung Devices - Samsung Toolkit

I'm not having any luck with this. I've followed the instructions step by step and when I flash a custom ROM, I get the dreaded yellow triangle of death apon rebooting. There were some other files mentioned in the links. Do I need to unzip those at some point?

sorry i have been away
Okay i am so sorry for the late response I have been away and very busy. This tutorial is how to root your samsung galaxy s3 (verizon) model sch-i535 because you need to unlock the bootloader for that specific model.
Now you mentioned that when you try to flash a custom rom you get a yellow triangle of death....
Have you unlocked the bootloader?
Is your phone already rooted? Are you trying to flash a custom rom or are you still trying to root your phone?
I hope you have already resolved your issue but if you haven't I would be more than happy to try and help you out.

How is it any easier then the other guides for jelly bean? Here you added the cf-auto root which is one extra step . Also with auto root there is a possibility of bricking the phone since it supports a lot of devices and as you are well aware that a lot of people new to flashing tend to flash the wrong files even if you give them a step by step guide. While this guide is helpful and does work it isn't as idiot proof as the other guide you linked on your post.

This does not work on my phone. When I try this, the phone boots normally. I have tried this several times and I get the same results. I can however hold the vol up button+the home button+the power button and get to stock recovery mode. I had an older S3 that this did work on but not my new one. I have read several threads here for rooting the S3 i535 with Jelly Bean 4.1.2 and this is supposedly the method but it will not work on my phone. What am I doing wrong? What am I missing? Please advise!

benbrown said:
This does not work on my phone. When I try this, the phone boots normally. I have tried this several times and I get the same results. I can however hold the vol up button+the home button+the power button and get to stock recovery mode. I had an older S3 that this did work on but not my new one. I have read several threads here for rooting the S3 i535 with Jelly Bean 4.1.2 and this is supposedly the method but it will not work on my phone. What am I doing wrong? What am I missing? Please advise!
Click to expand...
Click to collapse
This guide is different in that it uses cf-auto root so I highly doubt you even tried this method.

I finally did get it. All rooted now.
Sent from my SCH-I535 using Tapatalk 2

The easiest way to root is odin'ing Mr. Robinson's root injected tar and the unlock the bootloader. Done
Sent from my MIUI powered S3 thanks to StrumerJohn

maybe i should have been more clear...
faehsemc said:
The easiest way to root is odin'ing Mr. Robinson's root injected tar and the unlock the bootloader. Done
Sent from my MIUI powered S3 thanks to StrumerJohn
Click to expand...
Click to collapse
Hey everyone,
Well i guess everyone has their own favorite way of rooting their phone/device. I did not mean for this small tutorial to be the *absolute easiest* way to root a verizon samsung galaxy s3 model i535 i just thought that I could do people a favor by elaborating a bit more on certain steps to make the rooting process a bit easier.
On certain tutorials i found I didn't seem them clearly state that the VRLAC BOOTCHAIN file needed to go in the boot loader section of ODIN to unlock the phone's bootloader.
On other tutorials that show you how to use CF-AUTOROOT I didn't see any that told you that you needed to install SUPERSU from the google play store manually in order to fully utilize your phones rooted status.
Yes there are other ways too root a SGS3, the Samsung Toolkit is a good option, or using a custom root such as Cyanogenmod is another great option as well...
All of those options you will have to research for yourself and ultimately decide for yourself.
However, if you want to keep your phone's stock ROM and you just want to root your Verizon SGS3 model SCH-I535 then I like using ODIN + CF-AUTOROOT exploit.
All i wanted to do was assist and do my part on this great forum which has helped me so much in the past...
I hope it helped someone...
Thanks for everyone who replied and shared your thoughts on other rooting options.
-DroidShadow

droidshadow said:
Hello everyone,
Well this is one of my first tutorials for this forum on how to root your Verizon Samsung Galaxy S3.
I just recently got my Verizon Samsung Galaxy S3 and all of the tutorials I found were quite complicated and not very detailed so I thought that
I would write this tutorial and maybe it might help others out there....
Since the Galaxy S4 is getting ready to come out, the price has dropped considerably for the S3 and i believe more and more people will be getting this phone and wanting to root it.
Oh, and if you want an alternative guide you can use this very excellent tutorial from another post on this amazing forum:
http://forum.xda-developers.com/showthread.php?t=2046439
Here is the specs for the phone I am using and the step by step process I used to root it.
Verizon Samsung Galaxy SIII model I535 running Android 4.1.2
Okay step 1 you are going to need some files...
First thing you are going to need is the Samsung Drivers so you can connect your phone to your computer and your computer can recognize it.
All of the files you are going to need I am just going to reference the link from the other tutorial that I posted above, no sense in redoing work
that has already been done especially if it has been done well!
1. You can get the samsung driver files here: http://forum.xda-developers.com/showthread.php?t=2046439
click on the link that says samsung drivers
2. You are going to need Odin you can get it from the same link, click on the Odin Link
3. You are going to need the VRALEC BOOTCHAIN you can get it from the link I posted in step 1 make sure you get this file it is very
important.
Since I am using a Verizon Samsung Galaxy S3 the bootloader comes by default locked so we need this file to unlock the bootloader
so we can root the phone. If we were using any other phone besides Verizon we would not have to worry about this but since I have
Verizon I have to do this. IMPORTANT: if you are not using a VERIZON PHONE DO NOT download this file or use it in the step
process you do not need it.
4. Next you are going to need the exploit so that you can root your phone and you can grab that from a different website, here is the address:
http://autoroot.chainfire.eu/
This is the CF-AUTOROOT file and this is what roots your phone. If you have the same phone as me scroll down to the SCH-I535 link and
download that file.
Okay now that we have all of that downloaded lets get things moving...
First thing we are going to need to do is install the Samsung USB drivers, so do that.
After the drivers are installed plug in your phone and make sure that it connects to your computer correctly, after it connects disconnect
your phone from your computer.
Next thing we are going to need to do is extract the ODIN zip file and install the Odin executable.
Now we need to get to the critical stuff...
Step 1. Make sure that [USB Debugging] is enabled in your phone, if it is not go to Settings -> Developer Options and enable it.
Step 2. Put your phone in DOWNLOAD Mode. You do that by pressing Volume Down + Home + Power button and hold it down till you see
a warning screen. When you see the warning screen hit Volume Up to allow Download mode.
Step 3. Now that your phone is in Download Mode you are going to connect your phone to your computer with ODIN RUNNING if
everything connects correctly you will see ODIN highlight yellow (older versions of ODIN) or highlight blue (newer ODIN versions)
Step 4. Now this is where previous tutorials kind of messed up in my opinion (just my opinion). Now that your phone is in download mode
you need to only have the "auto boot" option selected in ODIN and click on the bootloader button and select the VRALEC file
you downloaded earlier. Every tutorial i read said to use this file with the PDA button/option but you need to use it with the bootloader
button/option in ODIN. Now that you have the VRALEC file selected under bootloader in ODIN select START. This will reboot your
phone and if everything goes correctly your phone's bootloader will be unlocked.
After reboot make sure to disconnect your phone from your computer.
Step 5. After your phone reboots from step 4 turn off your phone and then boot it back into DOWNLOAD mode. Vol Down + Home + Power
Step 6. Now that your phone is in Download Mode again (Reconnect your phone to your computer) and make sure ODIN is still running
Step 7. With your phone connected go to the PDA option/button and when you select it choose the CF-AUTOROOT file you downloaded earlier
Step 8. With your PDA option selected hit start. When this happens your phone will reboot and your will see a CUSTOM lock icon on your
screen don't worry it is okay. Now you will see some new text on your phone and if everything is working you will see things like
"Android is UPDATING"
Your phone is now rooted! but you are not done...
This is where all of the other tutorials I found also fell short...
Your phone is rooted but it will not work correctly without SuperSU
Step 9. Go to the Google Play Store and Download SuperSU. When the download is complete run SuperSU and now your phone is fully
rooted. You can test it by downloading Android Terminal and running the terminal and typing "su" or by downloading a root required
app Titanium Backup.
Congrats on rooting your phone! I hope this tutorial has helped you and I want to thank all of the system administrators of this forum and all of
the great guys and gals that contribute to this place. You guys/gals are what makes the open source community great!
I thank you all...
Hope it helped!
-droidshadow
Click to expand...
Click to collapse
Followed all instructions, and the phone never rebooted. Not its not turning on. Tried vol up+home+power, vol down+home+power, battery pull, holding down power for 2 minutes. . .
The only thing I can think of is that I possibly unplugged the phone before the reboot after Step 4, just as soon as the phone shut down and before the actual reboot.
Anything you can help me with? I''m going crazy here.
Thanks

Rooting and installation on S3 GTI9300
I rooted my S3 2 days back (i think so), now i want to install a custom rom (mostly xperia Z) and I am new to this world, so can you plz help me??
I followed your instructions there was no such msg as Andriod is Updating, and how should i do install the rom??
I wish to install from this http://forum.xda-developers.com/showthread.php?t=2174644

droidshadow said:
Hello everyone,
Well this is one of my first tutorials for this forum on how to root your Verizon Samsung Galaxy S3.
I just recently got my Verizon Samsung Galaxy S3 and all of the tutorials I found were quite complicated and not very detailed so I thought that
I would write this tutorial and maybe it might help others out there....
Since the Galaxy S4 is getting ready to come out, the price has dropped considerably for the S3 and i believe more and more people will be getting this phone and wanting to root it.
Oh, and if you want an alternative guide you can use this very excellent tutorial from another post on this amazing forum:
http://forum.xda-developers.com/showthread.php?t=2046439
Here is the specs for the phone I am using and the step by step process I used to root it.
Verizon Samsung Galaxy SIII model I535 running Android 4.1.2
Okay step 1 you are going to need some files...
First thing you are going to need is the Samsung Drivers so you can connect your phone to your computer and your computer can recognize it.
All of the files you are going to need I am just going to reference the link from the other tutorial that I posted above, no sense in redoing work
that has already been done especially if it has been done well!
1. You can get the samsung driver files here: http://forum.xda-developers.com/showthread.php?t=2046439
click on the link that says samsung drivers
2. You are going to need Odin you can get it from the same link, click on the Odin Link
3. You are going to need the VRALEC BOOTCHAIN you can get it from the link I posted in step 1 make sure you get this file it is very
important.
Since I am using a Verizon Samsung Galaxy S3 the bootloader comes by default locked so we need this file to unlock the bootloader
so we can root the phone. If we were using any other phone besides Verizon we would not have to worry about this but since I have
Verizon I have to do this. IMPORTANT: if you are not using a VERIZON PHONE DO NOT download this file or use it in the step
process you do not need it.
4. Next you are going to need the exploit so that you can root your phone and you can grab that from a different website, here is the address:
http://autoroot.chainfire.eu/
This is the CF-AUTOROOT file and this is what roots your phone. If you have the same phone as me scroll down to the SCH-I535 link and
download that file.
Okay now that we have all of that downloaded lets get things moving...
First thing we are going to need to do is install the Samsung USB drivers, so do that.
After the drivers are installed plug in your phone and make sure that it connects to your computer correctly, after it connects disconnect
your phone from your computer.
Next thing we are going to need to do is extract the ODIN zip file and install the Odin executable.
Now we need to get to the critical stuff...
Step 1. Make sure that [USB Debugging] is enabled in your phone, if it is not go to Settings -> Developer Options and enable it.
Step 2. Put your phone in DOWNLOAD Mode. You do that by pressing Volume Down + Home + Power button and hold it down till you see
a warning screen. When you see the warning screen hit Volume Up to allow Download mode.
Step 3. Now that your phone is in Download Mode you are going to connect your phone to your computer with ODIN RUNNING if
everything connects correctly you will see ODIN highlight yellow (older versions of ODIN) or highlight blue (newer ODIN versions)
Step 4. Now this is where previous tutorials kind of messed up in my opinion (just my opinion). Now that your phone is in download mode
you need to only have the "auto boot" option selected in ODIN and click on the bootloader button and select the VRALEC file
you downloaded earlier. Every tutorial i read said to use this file with the PDA button/option but you need to use it with the bootloader
button/option in ODIN. Now that you have the VRALEC file selected under bootloader in ODIN select START. This will reboot your
phone and if everything goes correctly your phone's bootloader will be unlocked.
After reboot make sure to disconnect your phone from your computer.
Step 5. After your phone reboots from step 4 turn off your phone and then boot it back into DOWNLOAD mode. Vol Down + Home + Power
Step 6. Now that your phone is in Download Mode again (Reconnect your phone to your computer) and make sure ODIN is still running
Step 7. With your phone connected go to the PDA option/button and when you select it choose the CF-AUTOROOT file you downloaded earlier
Step 8. With your PDA option selected hit start. When this happens your phone will reboot and your will see a CUSTOM lock icon on your
screen don't worry it is okay. Now you will see some new text on your phone and if everything is working you will see things like
"Android is UPDATING"
Your phone is now rooted! but you are not done...
This is where all of the other tutorials I found also fell short...
Your phone is rooted but it will not work correctly without SuperSU
Step 9. Go to the Google Play Store and Download SuperSU. When the download is complete run SuperSU and now your phone is fully
rooted. You can test it by downloading Android Terminal and running the terminal and typing "su" or by downloading a root required
app Titanium Backup.
Congrats on rooting your phone! I hope this tutorial has helped you and I want to thank all of the system administrators of this forum and all of
the great guys and gals that contribute to this place. You guys/gals are what makes the open source community great!
I thank you all...
Hope it helped!
-droidshadow
Click to expand...
Click to collapse
I ran ODIN with the bootchain, and that worked, but when i tried running it with PDA set to CF-autoroot file, I get SECURE CHECK FAIL

hello everyone
bgenchel said:
I ran ODIN with the bootchain, and that worked, but when i tried running it with PDA set to CF-autoroot file, I get SECURE CHECK FAIL
Click to expand...
Click to collapse
bgenchel: what kind of phone do you have? Are you 100% sure that you downloaded the correct CF-autoroot file for your specific phone model?

mlev1987 said:
Followed all instructions, and the phone never rebooted. Not its not turning on. Tried vol up+home+power, vol down+home+power, battery pull, holding down power for 2 minutes. . .
The only thing I can think of is that I possibly unplugged the phone before the reboot after Step 4, just as soon as the phone shut down and before the actual reboot.
Anything you can help me with? I''m going crazy here.
Thanks
Click to expand...
Click to collapse
Did you run the Odin with the VRLAC bootchain file then you unplugged your phone before a full restart could take place? This is a very sensitive issue because that bootchain file unlocks your bootloader on your verizon phone. Your bootloader is everything to your phone. It controls how your phone starts and your phone can not work correctly if your bootloader became compromised in any way. I really hope you figured it out, and if you didn't maybe you could call your insurance company (if you have one) and get a new phone. If you are worried about rooting your phone again you could look on craigslist, there are always people/professionals willing to do it for very reasonable prices $10-$20. Again i really hope you figured this out and if you give me some more details maybe we can figure this out together.

Phone Rebel Method
This is the same method that Phone Rebel has on his YouTube channel for rooting d2vzw. This tutorial is missing one step that Phone Rebel covers, after running CF Auto Root, he flashes the corresponding bootchain file that goes with whatever firmware your phone is running. When I rooted, I was running VRBMB1, so I flashed that boot chain following the other two odin flashes. http://www.youtube.com/watch?v=K4b9hcWHrW8&feature=share&list=FL8Y3FM4mtznp0GQbwkkwaSg
What I've learned is that CF Auto Root does not unlock the bootloader and trying to flash a custom ROM with result in the dreaded triangle message every time. I was given this method: http://droidviews.com/2013/root-and...erizon-galaxy-s3-sch-i535-android-4-1-14-1-2/
to try instead. In this method you flash the VRALEC, then CWM recovery, then you can flash SuperSU with an unlocked bootloader via CWM, then flash the final bootchain file depending on the firmware you're running. Method 3 contains the casual root tool, but I've seen mixed reviews for that one.
At the suggestion of someone on the Google+ community for the SGS3, I"m gonna attempt to root VRBMF1 (JB 4.1.2 w/multiwindow) via method 1 and then flash the VRBMB1 bootchain for the previous version and see what happens.

UPDATE
ohemetophobia said:
This is the same method that Phone Rebel has on his YouTube channel for rooting d2vzw. This tutorial is missing one step that Phone Rebel covers, after running CF Auto Root, he flashes the corresponding bootchain file that goes with whatever firmware your phone is running. When I rooted, I was running VRBMB1, so I flashed that boot chain following the other two odin flashes. http://www.youtube.com/watch?v=K4b9hcWHrW8&feature=share&list=FL8Y3FM4mtznp0GQbwkkwaSg
What I've learned is that CF Auto Root does not unlock the bootloader and trying to flash a custom ROM with result in the dreaded triangle message every time. I was given this method: http://droidviews.com/2013/root-and...erizon-galaxy-s3-sch-i535-android-4-1-14-1-2/
to try instead. In this method you flash the VRALEC, then CWM recovery, then you can flash SuperSU with an unlocked bootloader via CWM, then flash the final bootchain file depending on the firmware you're running. Method 3 contains the casual root tool, but I've seen mixed reviews for that one.
At the suggestion of someone on the Google+ community for the SGS3, I"m gonna attempt to root VRBMF1 (JB 4.1.2 w/multiwindow) via method 1 and then flash the VRBMB1 bootchain for the previous version and see what happens.
Click to expand...
Click to collapse
You can use method 1 outlined in the droidviews link i posted yesterday to root the phone and when you get to the point where you're flashing the second bootchain you can flash VRBMB1 instead of needing VRBMF1 and it will work just fine! I also believe this method will truly unlock the bootloader for flashing custom roms, to avoid the yellow triangle of frustration, but I have no oversight on this as it was not my plan to do so.

VRBMF1??
I must admit that I am new to rooting.
I just bought a new S3 i535 with 4.1.2 and would like to root it. In the link provided there are files to download. One of these files are the bootchain... When I look in my settings, I see VRBMF1 and in the link provided I see.............
For VRBLK3 (Jelly Bean 4.1.1) Link
MD5: E3A1CB07DE214ED8081ED9D42C9BAF4A
For VRBMB1 (Jelly Bean 4.1.2) Link
MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1
For VRBMD3 (Jelly Bean 4.1.2) Link
MD5: 9CB65EAE8784807349EC3D4FF3A0AAEF
I am confused on what to do. I would imagine that this instructional post was created before I got my phone (07/13/2013) and thus is the reason why it might be missing from the instructions. Please advise me.

BKSinAZ said:
I must admit that I am new to rooting.
I just bought a new S3 i535 with 4.1.2 and would like to root it. In the link provided there are files to download. One of these files are the bootchain... When I look in my settings, I see VRBMF1 and in the link provided I see.............
For VRBLK3 (Jelly Bean 4.1.1) Link
MD5: E3A1CB07DE214ED8081ED9D42C9BAF4A
For VRBMB1 (Jelly Bean 4.1.2) Link
MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1
For VRBMD3 (Jelly Bean 4.1.2) Link
MD5: 9CB65EAE8784807349EC3D4FF3A0AAEF
I am confused on what to do. I would imagine that this instructional post was created before I got my phone (07/13/2013) and thus is the reason why it might be missing from the instructions. Please advise me.
Click to expand...
Click to collapse
Yes, the instructional post was created prior to you getting an S3. So, if you got into Settings> About Phone and look at your baseband version you'll probably see I535VRBMF1 and you'll probably see it again in another field just below it. This indicates that you're running the VRBMF1 firmware. That is JB 4.1.2 with multi-window. When using the root process in the droidviews article it outlines flashing VRALEC, then CWM touch, then using CWM to flash the supersu file, then flashing either VRBLK3, VRBMB1, or VRBMD3. Since none of those bootchain files match your firmware and there is no VRBMF1 bootchain on the forums, I flashed VRBMB1 since it was the the bootchain from the previous firmware. It worked. I successfully achieved root with no problems. Hope this helps.

[ROOT/GUIDE] SM-T210R For Dummies, or Rom display issues

Talking ROOT SM-T210R SIMPLE and Easy, 8gb, White
Okay so I've been at it for days and i mean like months.... when I first bought my 8 gb white Samsung galaxy tab 3 Kernel 3.4.5, android 4.1.2, model JZ054K.T210RUEAMK1 and all i have been running into is problems, like jittery display issues, or flickering display, I tried every method but none has worked but i finally found one and got it all working and running, First of all i would like to thank gr8nole for this method, and all who have helped him. So first let me explain the most easiest explanation for dummies like me, or noobs,
NOTE: KIES, will fix any display issue and bring you back to your original rom, i forget to add this, because ours is the pain in the bottom, to get it to work correctly, it go download, http://www.samsung.com/us/kies/, download windows version then follow this method, http://www.samsung.com/us/support/faq/FAQ00048586/52928, then it will get you back to basic then make sure to check usb debugging
Just and example video for visual learners http://www.youtube.com/watch?v=Xolmt...ature=youtu.be, but you want to click on the files i suggested on the bottom lol not what he has on his screen xD
Must Have: KIES, make sure you have fully updated rom from samsung themself which can be found on kies (http://www.samsung.com/us/support/faq/FAQ00048586/52928) use this method, when you plug it in and update firmware, which your android should be on 4.1.2 and version because that's what i have
1. First lets Get all the files we need, First go download SM-T210.CWM.6.0.4.5.recovery.tar.zip at his xda post http://forum.xda-developers.com/showthread.php?t=2433853, after you have download that you will a friend name odin, which can be found here http://forum.xda-developers.com/showthread.php?t=2189539 (With odin you only want to use v3.07) and nothing else , Last but not least, you want this file from gr8ole android-armeabi-universal-root-signed.zip and save that to your sd card or ext while click on usb debugging or wherever you wanna store in on tablet
so you should have odin 3.07
T210.CWM.6.0.4.5.recovery.tar.zip (lol make sure to extract this file so odin can see it xD)
android-armeabi-universal-root-signed.zip
2. Use the same method as g8nole and minor adjustments
Instructions:
1. Download ODIN on your computer (just do a google search to find it...version 3.07 will work fine). http://forum.xda-developers.com/showthread.php?t=2189539
2. Power off the device.
3. Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
4. Hit the "Volume Up" to enter download mode.
5. Start the ODIN exe program using admin rights which means right click run as admin. I recommend un-checking Auto Reboot. DO NOT CHECK RE-PARTITION!!, LEAVE UNCHECKED!! YOU BEEN WARNED (which it already should be). See notes about ODIN below.
6. Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them) which can be found here http://www.samsung.com/us/kies/.
7. Select "PDA" then choose the T210.CWM.6.0.4.5.recovery.tar.zip.
8. Hit "START"
9. Wait for device to restart. Which means wait til odin says OKAY in the white box and the Picture ask you to reset, When the download icon on your tablet, and under download updates is full bar, and odin says reset!, just unplug it. then restart by holding the power button down, with vol up, and home, once the samsung picture shows, just let it run and onces its on put the zip file andriod universal root in any place you like, then reboot while holding the power, vol up, home, then only hold the up vol button when you see the logo, while also holding the home button, recovery mode should now be on. Select install zip, and locate the android-armeabi-universal-root-signed.zip)navigate with the up down volume button and power button to select file, whichever you placed in sd, or exsd,
10. When all is done reboot device, then it will update your android once you turn it on, Now the anoying part, It will be rooted but what google play won't connect?, easy fix , first lets just update all the binaries since its already rooted in supersu app,
Google Store Fix, now first you have to delete your some things, your apps wont dissapear or nothing as long as you dont uinstall them, go to settings<application manager<all<google play store<clear data/cache w.e<force stop<uninstall updates<it will then ask you it will be factory installed<yes, next step, delete your gmail account if you haven't done so, now go to your time settings (Date and Time) and change it to recent date whichever today is , then open play store and it will ask you to sign in again, blah blah google needs sign up and it should be up and running
ALL DONE, remember this is for people who have run into flicker display problems, which is caused by kernal issue with our model, but with stock rom itself we can universally root it through odin with just that simple method which took me like 3 mins lol to do
Grats guys! you have root and cwm now who doesn't want that enjoy and thanks to developers hard work! and my ambition!

Great guide. My friends SM-T210R kept getting kernal panic mode and the flickering screen. I did the same thing you did except I also installed Rocket Tab rom and Blackhawk kernel. It still Crashes every couple hours. I never could get the stock Kernal + Rom to work not sure what I was doing wrong. Perhaps I will follow your guide exactly this weekend.

morfn said:
Great guide. My friends SM-T210R kept getting kernal panic mode and the flickering screen. I did the same thing you did except I also installed Rocket Tab rom and Blackhawk kernel. It still Crashes every couple hours. I never could get the stock Kernal + Rom to work not sure what I was doing wrong. Perhaps I will follow your guide exactly this weekend.
Click to expand...
Click to collapse
thanks a lot this is my first guide i ever created in my life really lol so its kinda jumping around the place but this will root your samsung white, 8gb, and you wont get the display issue, and then download gl to sd with a 32gb card my god i can fit so many stuff, im so freaking happy, i found this method out, but im addding more stuff to it so you can start from scratch if your tablet can get in download mode then its never broken, i tested this like 15 times already, its been working fine for me, i was just trying to get step by step as low as possible

I'm trying to follow the instructions for the Kies restore.
I keep getting this error however. (Yes USB debugging is enabled. I also tried doing it from Download Mode)
{
"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"
}

James1o1o said:
I'm trying to follow the instructions for the Kies restore.
I keep getting this error however. (Yes USB debugging is enabled. I also tried doing it from Download Mode)
Click to expand...
Click to collapse
OK, I could be wrong... I just got the tab 3 for my daughter and haven't done anything to it yet.
But from my S2 experience.... And this might be incorrect because I can say I never ever really used kies..... But I don't think keis will work anymore on a rooted device with a custom recovery ? It could be I'm wrong, that it won't work with a custom Rom tho... Maybe it should work with custom recovery and root.... But I thought it didn't.
Anyway, don't know if there's a file out there for this device, but I've always just used Odin to return to stock. I never used kies. Cause kies is an unstable, unreliable mess.
Anyone feel free to add to what I've said..... Or correct me tho.
Sent from my XT1058 using Tapatalk

kj2112 said:
OK, I could be wrong... I just got the tab 3 for my daughter and haven't done anything to it yet.
But from my S2 experience.... And this might be incorrect because I can say I never ever really used kies..... But I don't think keis will work anymore on a rooted device with a custom recovery ? It could be I'm wrong, that it won't work with a custom Rom tho... Maybe it should work with custom recovery and root.... But I thought it didn't.
Click to expand...
Click to collapse
I used to have an S3. From download mode, Kies would always restore it fine. Also I have stock rom and recovery when I tried to run Kies. I was simply trying to get back to my countries proper rom. (Which I can't download because SamMobile download hosts are awful)
I even emailed Samsung about it, they got back to me this morning. They told me to reinstall Kies, if that doesn't't work take it to a Samsung support center.

James1o1o said:
I used to have an S3. From download mode, Kies would always restore it fine. Also I have stock rom and recovery when I tried to run Kies. I was simply trying to get back to my countries proper rom. (Which I can't download because SamMobile download hosts are awful)
I even emailed Samsung about it, they got back to me this morning. They told me to reinstall Kies, if that doesn't't work take it to a Samsung support center.
Click to expand...
Click to collapse
Well, would be much simpler if there is an Odin flashable version out there. Saves allot of headaches.
Kies is just awful.
Sent from my XT1058 using Tapatalk

kj2112 said:
Well, would be much simpler if there is an Odin flashable version out there. Saves allot of headaches.
Kies is just awful.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
The sad thing is, there is only one place I can get it. SamMobile...and its hosted on Terafile. Everyone on the site is complaining about it, but they seem to be refusing to change because they get money through affiliate program.

James1o1o said:
The sad thing is, there is only one place I can get it. SamMobile...and its hosted on Terafile. Everyone on the site is complaining about it, but they seem to be refusing to change because they get money through affiliate program.
Click to expand...
Click to collapse
Well.... At least you have answered a question I had. Just root and use stock system.... Or flash anything on it. I'll stick with stock. Just want to root to control the device better.... Battery issues in particular. My daughter is 5....she doesn't care about the Android version or touchwiz. Lol
Sent from my XT1058 using Tapatalk

my bad i was busy with work but, kies just gets you back to stock version, and this is for sm-t210r, which i rooted from stock version using this method, but it seems you have sm-t10 regular, if you have that, odin would do just fine this is for your model, this method is for sm-t10R, and model number

kj2112 said:
OK, I could be wrong... I just got the tab 3 for my daughter and haven't done anything to it yet.
But from my S2 experience.... And this might be incorrect because I can say I never ever really used kies..... But I don't think keis will work anymore on a rooted device with a custom recovery ? It could be I'm wrong, that it won't work with a custom Rom tho... Maybe it should work with custom recovery and root.... But I thought it didn't.
Anyway, don't know if there's a file out there for this device, but I've always just used Odin to return to stock. I never used kies. Cause kies is an unstable, unreliable mess.
Anyone feel free to add to what I've said..... Or correct me tho.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
yea depends what he has though if he has sm-t210 then just use odin but using odin with a pre-rooted will get you flickering screen on sm-210R, if you have regular then you have to go a different route to restore it back to normal, if you have a flicker screen problem or any problem, then the kies method i have will recover it, in kies just use the update tab on sm-t210 and it will recover to stock thats all or use odin, your choice. if you want to root sm-t210 the method is here http://forum.xda-developers.com/showthread.php?t=2433853, this will root yours np ^^

biggyhead said:
yea depends what he has though if he has sm-t210 then just use odin but using odin with a pre-rooted will get you flickering screen on sm-210R, if you have regular then you have to go a different route to restore it back to normal, if you have a flicker screen problem or any problem, then the kies method i have will recover it, in kies just use the update tab on sm-t210 and it will recover to stock thats all or use odin, your choice. if you want to root sm-t210 the method is here http://forum.xda-developers.com/showthread.php?t=2433853, this will root yours np ^^
Click to expand...
Click to collapse
Thanks for the info!
Sent from my Moto X cell phone telephone.....

Thanks

Question. I followed the instructions which are more or less the same as what I did to root my S4. When I enter download mode in the device and open Odin (v3.047) and I select the folder where I downloaded the CWM file, T210.CWM.6.0.4.5.recovery.tar.zip, I am not able to see that file in the selection.
Odin itself does not recognize the .zip extension as a valid file type for PDA files so is this simply an issue of renaming that file and removing the .zip from the extension? If so then the OP needs to be corrected to include this step because otherwise people will sit there wondering why this same thing is happening to them.
For reference Odin PDA File extensions are *.tar, *.md5, *.smd, *.gz and *.tgz.

demonr6 said:
Question. I followed the instructions which are more or less the same as what I did to root my S4. When I enter download mode in the device and open Odin (v3.047) and I select the folder where I downloaded the CWM file, T210.CWM.6.0.4.5.recovery.tar.zip, I am not able to see that file in the selection.
Odin itself does not recognize the .zip extension as a valid file type for PDA files so is this simply an issue of renaming that file and removing the .zip from the extension? If so then the OP needs to be corrected to include this step because otherwise people will sit there wondering why this same thing is happening to them.
For reference Odin PDA File extensions are *.tar, *.md5, *.smd, *.gz and *.tgz.
Click to expand...
Click to collapse
it was the link towards yours, which is the tar file, which popped up on mine when i used odin 3.07, thats actually interesting, because i redid the steps and it showed up, let me look at it again, and thanks to you we can do this

demonr6 said:
Question. I followed the instructions which are more or less the same as what I did to root my S4. When I enter download mode in the device and open Odin (v3.047) and I select the folder where I downloaded the CWM file, T210.CWM.6.0.4.5.recovery.tar.zip, I am not able to see that file in the selection.
Odin itself does not recognize the .zip extension as a valid file type for PDA files so is this simply an issue of renaming that file and removing the .zip from the extension? If so then the OP needs to be corrected to include this step because otherwise people will sit there wondering why this same thing is happening to them.
For reference Odin PDA File extensions are *.tar, *.md5, *.smd, *.gz and *.tgz.
Click to expand...
Click to collapse
yea so its odin v3.07 and it is basically your steps lol, like every detail, but just a twist for our model sm-t210R model k, this method is for basically anyone who messed up their tablet because they did the prerooted version for sm-t210r,

Yeah, I thought it would be a quirk. I used an older version when I was mucking around with my GS4 and had a similar issue but by removing the .zip in the file name it recognized it and worked. My work around with this one though was unzipping the file contents and pointing to the unzipped file. Never a dull moment.
For a while it was a scare though yesterday because something screwed up with recovery and I got the dreaded screen flicker and could not find a way to correct it. Not only that but I was already having issues with recovery that I could not get any of them to install. I kept getting permission issues. I ended up blind guessing things and was able to fix it by using TWRP 2.6.3 MK1 then when that was fixed I used ODIN to install the T210RUEAMK1_T210RXACAMK1_XAC to get things back to stock'ish. From there I was finally able to root the device with the universal-root-signed-zip.
This nightmare has me gun shy and I am hesitant to even want to attempt a custom ROM now. I've successfully rooted my wife's HTC Sensation which was a series of hoops, my previous GS2, GS3 and the GS4 without ever so much as a hiccup. My personal phones I am a ROM whore. When I installed the triangle away last month and checked the counter on the GS4 I had 31 on the counter.. in four months. Unless there is a bullet-proof ROM for this pad I don't see it happening. It blows, I may unload it and get something different that is not so much of a mess.
Thanks for the replies guys.

demonr6 said:
Yeah, I thought it would be a quirk. I used an older version when I was mucking around with my GS4 and had a similar issue but by removing the .zip in the file name it recognized it and worked. My work around with this one though was unzipping the file contents and pointing to the unzipped file. Never a dull moment.
For a while it was a scare though yesterday because something screwed up with recovery and I got the dreaded screen flicker and could not find a way to correct it. Not only that but I was already having issues with recovery that I could not get any of them to install. I kept getting permission issues. I ended up blind guessing things and was able to fix it by using TWRP 2.6.3 MK1 then when that was fixed I used ODIN to install the T210RUEAMK1_T210RXACAMK1_XAC to get things back to stock'ish. From there I was finally able to root the device with the universal-root-signed-zip.
This nightmare has me gun shy and I am hesitant to even want to attempt a custom ROM now. I've successfully rooted my wife's HTC Sensation which was a series of hoops, my previous GS2, GS3 and the GS4 without ever so much as a hiccup. My personal phones I am a ROM whore. When I installed the triangle away last month and checked the counter on the GS4 I had 31 on the counter.. in four months. Unless there is a bullet-proof ROM for this pad I don't see it happening. It blows, I may unload it and get something different that is not so much of a mess.
Thanks for the replies guys.
Click to expand...
Click to collapse
i feel ya man, i been messing around with roms also only one i got to work was rocket lite, but that gave me a few bugs, so i just recovered back to rom, the only reason i used kies because when i would go to the samsung site to get the file for it, it was busy and would never download, so i found this method to just root our sm-t210R model K, so far i can't even get kernals to work either, like for exp cwm, you need that version or your screen flickers, its really anoying, unless you have that one, truthfully i think the most hard models to root or install rom, there are certain types of cwm, rom, etc just for it. Like how odian 3.07 only works with the cwm file, i used the new one but i get a bad screen or it doesn't even load...pretty much a big middle finger

Yeah, it kind of sucks and after coming from the S4 being able to pretty much throw everything at it and it works including the first versions of 4.4.. this tab has been a pretty big let down for me. I was going to try Rocket Tab but the download time is ridiculous so going to give Crash ROM an at bat next.

biggyhead said:
my bad i was busy with work but, kies just gets you back to stock version, and this is for sm-t210r, which i rooted from stock version using this method, but it seems you have sm-t10 regular, if you have that, odin would do just fine this is for your model, this method is for sm-t10R, and model number
Click to expand...
Click to collapse
I don't understand why it would though.
SM-T210 and SM-T210R are identical except the R model has infrared. Everything else is identical.

[Q] Need to unroot my Samsung Galaxy Note 2

Hi everyone, i have recently bought used Samsung Galaxy Note 2 N-7100. Its currently on 4.1.1 but when i try to update its firmware it gives this error "Your device has been modified. Software Updates are not available" after this error i came to know about rooting/unrooting. I have read few tutorials and watch too but didnt see any positive feedbacks from people who have used them. so please let me know is there any safe procedure of unrooting my phone, it has super user app installed + in device status its says "modified" . I will be really gald if someone could help me as i want to go back to stock software.

jst728 said:
Hi everyone, i have recently bought used Samsung Galaxy Note 2 N-7100. Its currently on 4.1.1 but when i try to update its firmware it gives this error "Your device has been modified. Software Updates are not available" after this error i came to know about rooting/unrooting. I have read few tutorials and watch too but didnt see any positive feedbacks from people who have used them. so please let me know is there any safe procedure of unrooting my phone, it has super user app installed + in device status its says "modified" . I will be really gald if someone could help me as i want to go back to stock software.
Click to expand...
Click to collapse
Yes, you would need to download a software called Odin. You also need to download a compatible firmware. You stated you have a N-7100. Your firmware should be available here. Simply search for N7100. If you do not see yours listed, please let me know.
If you do find it, put your phone into download mode (hold Vol Down + Home + Power), open up Odin on your computer, then plug your phone to your computer, in Odin, select the "PDA/AP" tab, a window will popup, select the file you downloaded (it will be in a .tar format, if it is in .zip, simply extract it and you will find the .tar file), wait a few seconds while it checks the file. Once it is ready, select start. It will take several minutes to finish and you will be back to 100% stock. You will be able to update your phone without receiving that error. Hope that helps.
EDIT: Here is a video I found that may be useful. It is step by step.
http://www.youtube.com/watch?v=OdSpibu-WWs

unrooting N7100
You don't provide enough information (stock /custom rom, reasons for unroooting,...) for an easy answer imho.
Don't deem me rude ... but to my reckognition it's the best way to start with learning 'how do I make good use of web & forum search mechanisms' - before trying to mess with some complex devices' firmware.
Most probably you'll want to continue reading here: http://forum.xda-developers.com/showthread.php?t=1896696
Edit: someone was faster ... and more polite than me

jst728
xdapowerapps said:
Yes, you would need to download a software called Odin. You also need to download a compatible firmware. You stated you have a N-7100. Your firmware should be available . Simply search for N7100. If you do not see yours listed, please let me know.
If you do find it, put your phone into download mode (hold Vol Down + Home + Power), open up Odin on your computer, then plug your phone to your computer, in Odin, select the "PDA/AP" tab, a window will popup, select the file you downloaded (it will be in a .tar format, if it is in .zip, simply extract it and you will find the .tar file), wait a few seconds while it checks the file. Once it is ready, select start. It will take several minutes to finish and you will be back to 100% stock. You will be able to update your phone without receiving that error. Hope that helps.
EDIT: Here is a video I found that may be useful. It is step by step.
Click to expand...
Click to collapse
I went to SAM mobile website to download firmware but i couldnt find firmware for version 4.1.1 . Only version available for N-7100 is version 4.3 . What should i do now?

Would you please kindly READ http://forum.xda-developers.com/showthread.php?t=1896696
People who wrote this all-in-one manual for xda forum are no freaking dumb kids.
So READ this. As often as is necessary for you to understand.
Firmware versions 4.1.1 and 4.1.2 and 4.3 are available at SamMobile!
- Go to http://www.sammobile.com/firmwares/1/
- Enter you device data.
- Select & download firmware
- Continue at http://forum.xda-developers.com/showthread.php?t=1896696
- rtfm
Happy xMas anyway :|

A: Having Problems Rooting the Note Pro 12.2 SM-P900/905? TRY THIS!

**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!
3. Using your USB 2.0 cable and ports Install the Custom Rom "P900XXUANB3-RecoveryImg.tar" FIRST and flash it via ODIN 3.07 under the PDA checkbox that is "fixed" (so you noobs don’t make any soft bricks if this is your first attempt at rooting), and only use the ODIN 3.07 THAT COMES W/ CHAINFIRES AUTO ROOT .zip file and then unzip the folder to open ODIN 3.07 ONLY! This is only because I have read that there have been issues installing the SU via Chain Fires Auto Root Process... the file is called (currently as of 25 JUNE 2014) "P900XXUANB3-RecoveryImg.tar" PDA select it and then start when in DOWNLOAD MODE on your device. Manually select DOWNLOAD MODE if you have to BEFORE PRESSING START! Otherwise, one is just going to sit there and not accomplish anything.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
http://forum.xda-developers.com/attachment.php?attachmentid=2591159&d=1392930654
http://forum.xda-developers.com/attachment.php?attachmentid=2775098&d=1401644348
4 Reboot back into DOWNLOAD MODE. Flash in ODIN 3.07 with the PDA section and select this file next to install: "openrecovery-twrp-2.7.1.0-v1awifi.img.tar"
5. In DOWNLOAD MODE and flash the file under the PDA box TWRP (OR CURRENT RECOVERY OF YOUR CHOICE THAT IS AVAILABLE)
6. AGAIN... Restart your device into DOWNLOAD MODE via ODIN 3.07 and select PDA and then finally root this: "CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5" Then you can backup, restore, flash anything, and be happy! YOU SHOULD FINALLY HAVE A SUCCESSFUL ROOT! Turn off and REBOOT into RECOVERY to see if TWRP stuck and then reboot to see if the SU stuck. IF everything stuck reboot back into TWRP to flash whatever rom is available MAKE SURE TO BACK UP EVERY FILE BEFORE YOU FLASH ANY NON-STOCK ROMS. If not successful rinse wash and repeat until it does!
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
7. That’s it you should have root and a custom rom and recovery if you followed these instructions for flashing via ODIN 3.07 and Chainfires AutoRoot files. If you still have an issue repeat until root/recovery/Rom sticks. If you have to update the Binary for the SU just go to the Google Play Store and install the app and then try it again till it works. GOOD LUCK it worked for me this way!
**IMPORTANT**
BACK UP BACK UP BACK UP BACK UP after every flash that is possible to back up. If you can, back up the NON-SU stock ROM BEFORE installing SU, after installing the recovery and/or back up.
***IF I HELPED YOU OUT THANK ME***
DISCLAIMER - all research was observed via comments on the thread according to issues people have been having during ROOTING the device I simply have compiled the data and made a check list!

Need a link to the files you mentioned.

Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?

sstea said:
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
Click to expand...
Click to collapse
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.

Spere said:
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Click to expand...
Click to collapse
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks

sstea said:
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
Click to expand...
Click to collapse
You can always flash stock firmware via odin

I was just wondering if everyone was having a much easier time with achieving root now? Kies caused me to "Hang" a lot during the Root and custom rom to stick w root... as of right now i can not get the only ONE custom ROM that looks promising, i have found by GWatts (correct me if i am wrong and i apologize if i have typed the wrong screen name handle) i believe his handle is... at this point im not sure what i am doing wrong as of yet but im sure i am missing a step or i just need to start back at unroot back to stock firmware and try and try again lol. not saying anything is wrong with his work at all by any means because people other than me with the same device have gotten it to stick and im just wishing i could as well because its sweet looking ROM! NOT TO MENTION THE ONLY ONE THAT IS OUT (that is which i know about. i haven't been on in a few months idk), SO KUDOS TO WATTS i just haven't been successful at installing his custom rom just yet... Im hoping that its just going to need to be erased again and then reformatted after a factory reset and what not, i pray it sticks because his incorporation of the aroma installer was a nice touch and his ROM really looks good... Now if i can just get it not to stick at samsung boot logo and freeze id be good lol!

sanvara said:
Need a link to the files you mentioned.
Click to expand...
Click to collapse
ok

I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.

pnuker said:
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
Click to expand...
Click to collapse
**Edit**
I went back and reflashed the twrp file and it got me out of the error screen. I installed supersu, and then re-flashed the cf-auto-root file, and it worked like a charm. I'm not sure if it was the installation of supersu, or just repeating the process that fixed it, but I'm happy either way...

Thank you! I succesfully rooted my SM-P900 after all mentioned problems ( hanging in the cache.img and after a while a disturbed screen etc.) with your guide. I am a very happy rooter now.

Thanks,
Thanks to the poster. I tried rooting with the instructions from a few other sites and thought I bricked it,
Followed your instructions, and presto.. Rooted! :good:

Rooted!
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!

your welcome!
frankiecxyz said:
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
Click to expand...
Click to collapse
your very welcome! it took me a bit to get it down but i eventually figured it out and at the time information on rooting the device was hard to find with this specific model. then i discovered what the issues where and felt the need to post it! im glad i could help!:laugh:

Flash SU with TWRP not ODIN
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !

soft bricked
Hello!
First of all let me say that I'm a complete newbie, this is my first android device. I tried to root my SM-P900 (P900XXUANI1) using an online guide (image with URL attached, as I am not allowed to paste URLs)
Unfortunately at Step 10 (flashing with Odin) the operation failed and now I ended up with a soft bricked device (I assume this is the correct definition). It will only show the message asking me to connect it to KIES to recover it.
I know i can try to use KIES 3 and restore it, but before that i would like to ask if there is any alternative which will allow me to unbrick the device without losing all my data... (yeah i know...).
If i follow this guide will this help? I'm not sure if I can even put the device in download mode again as it shows the error message about connecting it to KIES...
At this point I don't care about rooting, I just want to unbrick the device.... I understand the guide up to (and including) step 3. But for the rest of the steps I'm lost Could anyone please explain them in a bit more detail? I don't want to install any custom firmware, just to unbrick it...
Any help would be very appreciated!
Thank you

Yemble said:
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
Click to expand...
Click to collapse
Have you got a link to the odin rwrp 2.7 you used and the su 2.7 flash for twrp please?

VenomousViper said:
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!.......
Click to expand...
Click to collapse
When i trying root, my SGN freeze in "cache". Odin show error and tablet goes to Emergency Firmware Recovery. Аnd it does not matter what program I use and how I do it.

Mine Reboots Constantly
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.

sunnykhs said:
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
Click to expand...
Click to collapse
Have you cleared dalvic cache and cache in TWRP recovery? Be forewarned the process takes a while for cache wipe.
Sent from my SM-P900 using Tapatalk

Database Info

welcome