Database Info

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.

[SGH-I337M] CF-Auto-Root [CANADIAN MODELS ONLY]

Check your device model ! Settings -> About device -> Model number. See the third post for exact supported model numbers. If your device is a totally different model, it will not work (may even brick) !
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock Samsung firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices (Galaxy S1, Galaxy Tab 7", Galaxy S2, Galaxy Note, Galaxy Nexus, Galaxy S3, and many more) and has clocked over 13 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Stock recovery
Installation and usage
Flash the CF-Auto-Root package as PDA in ODIN (details on how to do that are in next post), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
If you don't get to the red Android logo, boot into recovery manually ("adb reboot recovery", or boot while holding Power+VolUp+Home).
Using this root increases your flash counter. You should run Triangle Away (see below) after rooting to reset the counter. Note that if you want to run custom kernels or custom recoveries, your flash counter will be set to 1 at every boot. Either configure Triangle Away to reset the counter at every boot (Play version only) or only reset the counter when you need to go into warranty.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Why isn't this just called CF-Root
The traditional CF-Root's included a custom recovery (CWM, TWRP, etc) and were meant for devices that had a single kernel/recovery combination. CF-Auto-Root doesn't include a custom recovery and is meant for devices that have kernel and recovery separate (so you can manually install any custom recovery you wish). The Auto part comes from the fact that a large part of the process is automated (though it constantly needs adjusting)
Not included - Triangle Away
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.

ODIN Installation (detailed)
Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
You may now optionally want to install and run Triangle Away to reset the flash counter.

2013.05.20 --- CF-Auto-Root
SuperSU: v1.30
Download
SGH-I337M: CF-Auto-Root-jfltecan-jfltevl-sghi337m.zip
Other models
International Samsung Exynos GT-I9500: http://forum.xda-developers.com/showthread.php?t=2292615
International Qualcomm Snapdragon GT-I9505: http://forum.xda-developers.com/showthread.php?t=2219803
Sprint: http://forum.xda-developers.com/showthread.php?t=2291827
T-Mobile: http://forum.xda-developers.com/showthread.php?t=2294005
AT&T: Bootloader locked, do not use CF-Auto-Root on it
VZW: Bootloader locked, do not use CF-Auto-Root on it
History
2013.05.24: SuperSU v1.30

Worked wonderfully!
Sent from my SGH-I337M using xda app-developers app

Awesome work, any possibility of an ATT USA version? Just got my 32Gb Black Mist delivered today by UPS!

Exellent.
Perfect like always!!! UR the best

very nice thaks a lot i had my s4 almost 3 weeks i was wiating your post finly i got it today . love it so easy root it thanks again.
just i need to ask wen rooted s4 in stats says now custom not official if i flash Triangle Away it will come agian official in stats or not? thanks adv- .

one question, is this really easier than just installing samsung drivers, checking debug and pressing run.bat on motochopper??? if anybody thinks thats hard, maybe they need a motorola razr. I dont want to offend you chain because i love your work, but i dont understand why you invested time into this
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
wasimahmad said:
just i need to ask wen rooted s4 in stats says now custom not official if i flash Triangle Away it will come agian official in stats or not? thanks adv- .
Click to expand...
Click to collapse
Check this thread:
http://forum.xda-developers.com/showthread.php?p=41845225#post41845225

highaltitude said:
Awesome work, any possibility of an ATT USA version? Just got my 32Gb Black Mist delivered today by UPS!
Click to expand...
Click to collapse
ATT version has a locked bootloader, and you already need root to apply a hack to flash and run custom firmwares on it. As such, CFAR wouldn't be much use on it. It may be so at a later stage (amongst other things that would probably require a different bootloader unlock method than is used now) that you need an old ATT firmware to be even to unlock, then need something like CFAR to root a newer firmware, but for now that seems unlikely. And even if that were the case, it would still be confusing and people would try to use CFAR on their locked device which could result in brickage (worst case).
wasimahmad said:
very nice thaks a lot i had my s4 almost 3 weeks i was wiating your post finly i got it today . love it so easy root it thanks again.
just i need to ask wen rooted s4 in stats says now custom not official if i flash Triangle Away it will come agian official in stats or not? thanks adv- .
Click to expand...
Click to collapse
Triangle Away can work to reset "flash counter" and "binary status" (though the current version sometimes the modification doesn't stick - update coming). As I've explained a hundred times probably but nobody listens and everybody keeps repeating the wrong information: the custom system status is scanned by the Samsung firmware and set in the bootloader. One of two truly reliable way to keep that status set to official is to unroot and flash a stock firmware. There are some other workarounds (like some of the advanced options in Triangle Away) that will keep that value official *most* of the time, but nothing 100% foolproof longterm - no matter what others tell you. The other reliable way is to first have that value reset to official using a forementioned method, than flash a modified system that has all the detection stuff patched out and/or removed.
polish_pat said:
one question, is this really easier than just installing samsung drivers, checking debug and pressing run.bat on motochopper??? if anybody thinks thats hard, maybe they need a motorola razr. I dont want to offend you chain because i love your work, but i dont understand why you invested time into this
Click to expand...
Click to collapse
Exploit vs firmware root. Think about it for a while.

Was definitely hoping and waiting that you release this, awesome work as always!!!

Thank you for CF Auto Root! Any chance there will be support for the SGH-I337M in Mobile Odin?
Sent from my SGH-I337M using xda app-developers app

hi
MR Chainfire bundle of thanks for reply your triangle away works flawlessly brought my phone s4 from custom to official and zero binary. i selected both options: auto reset at boot and allowed tracker to run. Then i restarted the phone and it says counter zero and status official
thanks for all the help and your hard work.
---------- Post added at 05:15 AM ---------- Previous post was at 04:57 AM ----------
is that mobile odin pro dos sport s4 yet or not thanks adv. ?

Finally! Rooting Right Away, the only method I trust in and from the best developer out there. Thanks man!
:thumbup:
Sent from my SGH-I337M using xda premium

When you say Canadian models, does that include the Wind variants too.. or is that a different? Would I have to use the T-Mobile version for the Wind variant?

Any chance to support triangle away? I tried the one linked in OP and it didn't work
I see that you said it doesn't stick, is that the same as it just never working? It worked great on my S3 but on my S4 it just reboots and does nothing

10cheesecakes said:
When you say Canadian models, does that include the Wind variants too.. or is that a different? Would I have to use the T-Mobile version for the Wind variant?
Click to expand...
Click to collapse
Yes that includes Wind, all Canadian variants. Do not use the t-mobile one.

just curious you did not mention the i337m bootloader is locked. Therefore after we flash this through odin are we able to flash custom roms. Just curious. thanks

casualt said:
just curious you did not mention the i337m bootloader is locked. Therefore after we flash this through odin are we able to flash custom roms. Just curious. thanks
Click to expand...
Click to collapse
Yes. I would make a nandroid first off course.
Sent from my SGH-I317M using Tapatalk 2

I think canadian models don't have bootlock
Sent from my SGH-I337M using xda premium

Now just mobile Odin and we're on top of the hill....
JKAY DELUXE [I9300 JB 4.1.2]

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

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

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

[HELP]System software not authorized by Verizon.

I installed Rom Manager on my phone to install TWRP to flash a new rom
My Device is SAMSUNG GALAXY S3 VERIZON
After the installation of TWRP, I restarted my device
then the annoying message appeared
I look for some solution in Google but no luck
I tried going in to Download Mode but the key combination is not working
and when i press the key combination, It is only Black Screen and vibrating every second.
Is my device Hard-Bricked? How to bring it back to working again?
Please I need your HELP!! THANKS!!

What version of Android was the phone on?
Somewhere about 4.4.2 the bootloader got locked.
Go read the threads for SuperLiteROM and the special recovery for the locked bootloader.

Did you ever find a solution to this?
Sent from my SCH-I535 using XDA-Developers Legacy app

It's soft bricked, just need to run Odin and load a stock ROM back on. You probably have 4.4.2.

I already fixed it and using it now as i type....
THANK YOU ALL GUYS FOR THE EFFORT YOU'VE MADE....
i fix it by using a so called USB JIG and after it booted perfectly, i found out the problem was with the vol. flex

I've now been at this for 4 hours, with no luck. :C
I'm having the same error issue as OP.
I'll try to share as many details as I actually remember/have, because I'm not sure what's needed. I broke the phone trying to root it to make it an mp3 player and to remove bloatware. Being an idiot, I must have deleted something the phone needed. I'm an absolute a beginner at any and all things android rooting and flashing.
I have no idea, after so many hours have gone, by what exactly I uninstalled with Kingo. I've just been trying to reset the phone to the factory OS. I already tried a factory reset to no avail.
Apps I've installed throughout my attempts to fix this include: SuperUser, Official TWRP App, ROM Manager, BootDroid, Kingo ROOT, and Samsung Odin Download Helper.
The only thing I can do to start the phone up past the "Verizon software warning" screen is hold volume down, home, and power to bypass it to the booting screen.
The phone info
Samsung Galaxy s3
Model #: SCH-1535
Android Version 4.4.2
Baseband version: unknown
Kernal version: 3.4.0 [email protected] #1
Build number: kot49h.1535VRUDNE1
SE Android status: Enforcing SEPF-SCH-1535_4.4.2_0016
Hardware: 1535.10
64gb SD Card
ERRORS:
This one comes up twice on startup. "Unfortunately, the process com.android.phone has stopped."
If I use BootDroid to launch Bootloader, I get a green droid with this in the corner
ODIN MODE
PRODUCT NAME: SCH-1535
SYSTEM STATUS: Custom
QUAL.COMM SECUREBOT: ENABLE
BOOTLOADER AP SWAEV: 2
If I press volume down, home, and power it gives warning about installing a custom ROM and I can choose volume up to load the custom one, or press volume down to boot normally.
If I press up now, I get a screen saying this in the corner instead:
ODIN MODE
PRODUCT NAME: SCH-1535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUAL.COMM SECUREBOT: ENABLE
BOOTLOADER AP SWAEV: 2
And under a green droid it says "Downloading..." Do not turn off target!! But nothing happens, it just stays on this screen.
If I select Recovery mode in ROM Manager, it gives me the "System software not authorized by Verizon" screen.
Currently I have a file named I535VRBMF1_I535VZWBMF1_VZW.zip on the SD card, but it doesn't show up anywhere in the phone, only when I open the folder on my PC. When I choose "install ROM from sd card" in ROM Manager, the files aren't there. After the first try, I also added the files unzipped also, but they are also not visible.
I've tried Fix Permissions in ROM Manager. All of the apps listed above have root access. Then it says to reboot my phone, but nothing appears to have changed.
I don't remember everything I've tried, but I at least know tried How to Use ROM Manager to Flash Custom ROMs after Rooting via Kingo Root, for sure, but I couldn't get past
"Download the ROM you want and copy it to your phone's SD card.
Before you find the custom ROMs you should use your phone model to find your wanted Android version on Google. You should be aware that each ROM will be based on a specific Android version." because the files on the SD card won't show up on the phone.
Thanks in advance!

Yard-Paragon said:
I'm having the same error issue as OP. I'll try to share as many details as I actually remember/have, because I'm not sure what's needed........
Click to expand...
Click to collapse
Oh My.... This is a real mess... LMAO!
I will do my best to help you out but, I can't guarantee anything. I'm going to try to address this the best way I can since your post is really all over the place.
Let me just clarify 2 things:
1) Your device is currently on the NE1 firmware and you will not be able to flash the MF1 or any other firmware besides the NE1.
2) You had mentioned that you wanted to install a Custom Firmware on your device and unfortunately, you will not be able to Unlock your Bootloader since your on the NE1 Firmware and your Bootloader is locked up.
Your only option is to either:
A) Debloat, that requires careful consideration to figure out what can be removed and what can't. You'll be surprised at what odd apps the Firmware actually has a dependency on and can crash your device (as you've already experienced).
B) Install what's called the TW Based Firmware. This is the Stock Firmware that is specially customized with the appropriate debloated apps and a few other customizations that varies on the developers.
3) Finally... There's the "Kingo" that you used and, I'll get to the point, that's garbage. very few Succeed with this and is rarely used nowadays. We'll hopefully get back to rooting.
What it looks like is the possibility of your device being on the verge of being Hard Bricked...
You need to flash the NE1 Firmware and might need to use the PIT file (PIT = Partition Information Table) but, we'll start without the pit file first.
Go to the following thread and obtain the "I535VRUDNE1_I535VZWDNE1_I535VRUDNE1_VZW" Firmware for your device.
https://forum.xda-developers.com/showthread.php?t=3744627
Be sure to read the top portion of the OP (OP = The First Post) regarding what you need to have and know within the instructions for Flashing the Stock Firmware.
Please let me know where/how you're doing...
FYI... The TW Based Firmware are those that are either labeled with "TW" and/or "Debloated" on the Threads Title.
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

I fixed this a long time ago. I used a USB JIG because I found out the volume keys are not working. After using the JIG, I flashed the stock rom for Verizon S3 Android 4.4.2. Then it works. But I'm not using the device anymore. If anyone who still experience this problem, try USB JIG.