[SM-N910*] CF-Auto-Root - Galaxy Note 4 Q&A, Help & Troubleshooting

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, S2, S3, S4, Galaxy Note, Note2, Note3, dozens of Tab models, etc!) and has clocked over 32.5 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 and trips the KNOX warranty flag!
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.
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.

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!

Download
SM-N910F (International, Qualcomm): CF-Auto-Root-trlte-trltexx-smn910f.zip
SM-N910G (Asia, Qualcomm): CF-Auto-Root-trlte-trltedt-smn910g.zip
SM-N910H (Asia, Exynos): CF-Auto-Root-tre3g-tre3gxx-smn910h.zip
SM-N910T (T-Mobile USA, Qualcomm): CF-Auto-Root-trltetmo-trltetmo-smn910t.zip
SM-N910P (Sprint, Qualcomm): CF-Auto-Root-trltespr-trltespr-smn910p.zip
SM-N910R4 (US Cellular, Qualcomm): CF-Auto-Root-trlteusc-trlteusc-smn910r4.zip
SM-N910W8 (Canadia, Qualcomm): CF-Auto-Root-trltecan-trltecan-smn910w8.zip
SM-N910C (Thailand, Exynos): CF-Auto-Root-trelte-treltexx-smn910c.zip
SM-N910U (Hong Kong, Exynos): CF-Auto-Root-trhplte-trhpltexx-smn910u.zip
SM-N910K (Korea, Exynos): CF-Auto-Root-treltektt-treltektt-smn910k.zip
SM-N910L (Korea, Exynos): CF-Auto-Root-treltelgt-treltelgt-smn910l.zip
SM-N910S (Korea, Exynos): CF-Auto-Root-trelteskt-trelteskt-smn910s.zip
SM-N9100 (China, Qualcomm): CF-Auto-Root-trltechn-trlteduoszc-smn9100.zip
SM-N9106W (China, Qualcomm): CF-Auto-Root-trltechn-trlteduoszn-smn9106w.zip
SM-N9108V (China, Qualcomm): CF-Auto-Root-trltechn-trltezm-smn9108v.zip
SM-N9109W (China, Qualcomm): CF-Auto-Root-trltechn-trlteduosctc-smn9109w.zip
Other models
CF-Auto-Root is not yet available for all models - one stock firmwares for these models become available, let me know, and I'll make the corresponding CF-Auto-Roots. Make sure to check the main CF-Auto-Root site as well, as models may be listed there that are not listed here yet!

Thanks a bunch @Chainfire, fast and swift as always

Nice work! So quick

Thanks chainfire!! You're the greatest... Hope you'll have root for the N910F as soon as possible...

Yup thanks @Chainfire great stuff. Rooted my 910U this afternoon and all cool.

thank you so much!
it works

So fast, so dangerous. Tks you so much.

Well I honestly cant wait for my note 4 and its root
Thanks a ton Chainfire. Amazing as always

Thanks. Is there a way to root the device without voiding the warranty?

mine247 said:
Thanks. Is there a way to root the device without voiding the warranty?
Click to expand...
Click to collapse
Well, I think it's very diffient question for @Chainfire. Just do it with your own risk.
Sent from my SM-N910X using Tapatalk

n910 K
is it possible to root the korean version n910k ? its exinos (LTE-A) based...

Would this work on the AT&T version, or only if the bootloader is unlocked?

Things are looking up. I believe its posted on what device it will work on..gotta read people..lol
FirekatV8/FireGearXXX

Welcome and Thanks

I wonder if this would affect OTA updates?

pcman2000 said:
I wonder if this would affect OTA updates?
Click to expand...
Click to collapse
Me too. If the bootloader is locked, and yet this root still works, how would one update update things like firmware, radios, Android L when it comes, and things like that in the future? Assume I'm ok w stock ROM.

flyhighx said:
Me too. If the bootloader is locked, and yet this root still works, how would one update update things like firmware, radios, Android L when it comes, and things like that in the future? Assume I'm ok w stock ROM.
Click to expand...
Click to collapse
Well, the bootloader isn't locked - I believe CFAutoRoot works by flashing a custom recovery (which is why it needs Odin) which roots the device then restores to stock recovery.
I'm wondering if the recovery it restores to is fully stock, so that OTAs would work. Additionally, I wonder if the Knox flag disables otas.

all these questions will be answered very soon..if you are paranoid about voiding you warranty, then don't root..
"generally" speaking, if you have a custom recovery on your phone, you can not get OTA updates..

Related

[GUIDE] Canadians Root your i9000M!!!

After digging through XDA, there wasn't many root methods available to us Canadian users of the i9000m! This procedure roots your phone and installs ClockworkMod Recovery.
Requirements:
Your device must be running on the latest Gingerbread KG3 Firmware. If not, please update with Kies.
Samsung Drivers
1. Download the files (Found below)
Odin3-v1.85
KG3-CWM-Kernel.tar
2. Run Odin as an administrator. In Odin, select PDA and open the KG3-CWM-Kernel.tar file. Auto-reboot and F.reset should be the ONLY things ticked off. Do not close out of Odin.
3. Enter Download mode on your phone. Press VOLUME DOWN + HOME + POWER all together until you reach the download mode screen on your phone.
4. Plug in your download mode phone into the computer. Make sure Odin recognizes your phone. It will show up in the "ID:COM" on the left side to verify the connection. The text box should also say "Added!". Press start.
5. Do not touch your phone. Wait until your phone reboots to disconnect your phone. You should now see the new app SuperUser.
And that's it! This procedure will only take seconds. Now you can flash ROMS and update your phone to Jelly Bean.
To enter ClockworkMod, hold down VOLUME UP + HOME + POWER.
Thanks... was looking for that TAR file as a friend of mine wants to root his good ol' GS1
Works perfectly, Thank you.
I follow this guide but my phone keeps rebooting itself and the Galasy S screen keep showing up for about 3 seconds then it reboot again. Help!
kyle9788 said:
I follow this guide but my phone keeps rebooting itself and the Galasy S screen keep showing up for about 3 seconds then it reboot again. Help!
Click to expand...
Click to collapse
Were you positive your phone was the i9000M?
samgoalie17 said:
Were you positive your phone was the i9000M?
Click to expand...
Click to collapse
No, it was i9000 my bad. I manage to make it working again flashing the stock GB rom from Optus Australia. I'm sorry I never root the GS1 before this is my 1st time. Now it said firmware version is 2.3.6, baseband XWJW1, build XWJW6. How can I root it now?
kyle9788 said:
No, it was i9000 my bad. I manage to make it working again flashing the stock GB rom from Optus Australia. I'm sorry I never root the GS1 before this is my 1st time. Now it said firmware version is 2.3.6, baseband XWJW1, build XWJW6. How can I root it now?
Click to expand...
Click to collapse
You need to download the cf root from the android development section for your JW6 firmware.

[Q] Hong Kong 32GB n9005 and PIT

I want to flash an Aussie ROM on my HK 32GB n9005. I've been doing some reading and what I think I need to do is as follows...
ghibli3's thread at http://forum.xda-developers.com/showthread.php?t=2550823 specifically addresses this issue and thanks to those contributing there and elsewhere.
Now to check I understand what they are saying before I brick my phone.
I have these:
CSB_signed_HLTE_EUR_OPEN_32G_0718.pit
CSB_signed_HLTE_EUR_OPEN_32G_0805.pit
ghibli3-N9005.pit
ratcom-N9005.pit
I also used ghibli3's N9005-SaveMyPit from http://forum.xda-developers.com/attachment.php?attachmentid=2426123&d=1385903491 to get a copy of my current pit.
I have my original HK MI7 stock, a HK stock MK2 (used to root my phone originally using RDLV) and both an MI7 and MJ7 Aussie ROMs.
So... here is what I think I need to do... Please let me know if this is correct or tell me how to do it better.
Using Odin and with phone in DL mode, USB Debugging on, Samsung drivers and ADB setup on PC...
1. Load a PIT file in [PIT] in Odin and tick [Re-Partition] then [Start]
(1st question, do I reboot the phone or just go to the next step?)
2. Follow RDLV steps to flash the Aussie MJ7 to root the phone.
(2nd question, should I drop back to the MI7 version for the root operation? I don't think it is needed as when I rooted my phone with HK version, I had HK MI7 on the phone and used HK MK2 to root it)
(3rd question, I have Kies 3 on my PC - should I uninstall it before doing any of this or might it be helpful to have it still installed?)
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Journyman16 said:
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Click to expand...
Click to collapse
For using PIT file, you need to add the PIT to Odin when you flash so it'll repartition as it's flashing. However, don't take that as a solid cause I am not 100% sure myself as I haven't messed with PIT files (yet) - but from what I have read that is how it is done. - Have a scan through the HK bricked (solved) threads to be doubley sure cause yeah, it's easy to end up with a brick
Thanks for that. Kinda what I was planning to do but I'm not sure if I do the PIT flash first then do the rest or if I do it all as one process. I'll check out that thread... been looking anywhere I could find a PIT reference.
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Journyman16 said:
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Click to expand...
Click to collapse
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
So this gets a bit strange now... I downloaded Phone Info from Play Store and ran it. I did that because I noticed I was having Wifi issues - it was working but kept thinking it was off - I'd click it to turn it on and the button wouldn't go green, but I had signal in the Notification bar. Going to Recovery to clear cache showed it was now applying CSC-code as BTU instead of TGY, so SOMETHING worked when I was doing the PITs.
So, Phone Info shows my Region Code as BTU, my CSC country as UK/IRE and my CSC Country ISO as GBBut I have a mix of ROM info:
Bootloader: ZHUBMI7
Baseband: ZHUDMJ9
PDA: XXUDMK2
CSC: OXADMK2
So, PDA and CSC are from a UK MK2 I tried to use early on and failed with, while BL and BB are from the original HK MI7 (BL) and the HK MK1 I rooted with.
So my question is now, can I now flash a BTU or other normal ROM onto my phone, using the RDLV process to make sure I get root and don't trip Knox?
IIRC I think the process works up to MK2 (and certainly does to MK1 as that what I used originally) so I should be able to DL (say) XXUBMJ1 to use for the BL and use XXUDMK2 for the root process. (i.e. the same as I did using HK MI7 for the BL and HK MK1 for the root process)
3 questions:
1. Is it the PDA that determines the partition Hong Kong users have such problems with? Or is it the Bootloader?
2. Can anyone think of a reason why this would not work? (now my CSC is BTU)
3. Could I now use an Aussie ROM to run the RDLV process?
FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Journyman16 said:
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Click to expand...
Click to collapse
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
Unfortunately, PIT's don't seem to come easy. As above I have about 4 of them I tried. There seems a bit of a disconnect between what the AP/CP/CSC are and what the files in a ROM are e.g. in XXUBMH1 there's boot.img, recovery.img, system.img.ext4, userdata.img.ext4, persdata.img.ext4, persist.img.ext4 and in XXUBMI7 there's sbl1.mbn, aboot.mbn, rpm.mbn, tz.mbn, sdi.mbn, NON-HLOS.bin, boot.img, recovery.img, system.img.ext4, modem.bin, cache.img.ext4, hidden.img.ext4
While I've been around a while now, this seems to be a blank spot for me at present - how do I flash a CSC? From reading it seems some ROM.s come with 4 or 5 files, e.g. see attachment - but I haven't been able to find one yet. (the one in the pic was hosted on Hotfiles which is now defunct thanks to the Almighty USA draconian control freaks. )
Update: I think I have found a copy of it so I can try that when it finishes DL'ing.
Other than that, anyone know of where there might be another such ROM to DL? Also if I am flashing a CSC file do I flash the PIT as well (i.e. at the same time) or do the PIT first?
Which Odin options get ticked for a PIT? I tried [F. Reset Time] [Re-Partition] [Auto Reboot] [Nand Erase All] previously and it didn't seem to work. I saw a recovery type post that suggested ticking [Phone EFS Clear] but seems to me that is a tick towards Brick - and the Recovery being offered was to a KK ROM anyway.
FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Journyman16 said:
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Click to expand...
Click to collapse
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
FeralFire said:
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
Click to expand...
Click to collapse
Well, it let me flash the vega BTU MK2 ROM but now there's a wifi problem. Still waiting for cygwin to download so I can RDLV on the XSA ROM. There seems to be some kind of conflict between BTU and Australian settings. Says to turn on wireless and actually finds my SSID's but then doesn't connect properly. le sigh...
Well it's been coming up to 24 hours with no phone but I seem to have found my way.
The problem seems to have been a mismatch between BL, CSC and PIT. In trying to get off the Hong Kong set up I wound up with a ZHU BL, BTU CSC and XSA CP and AP. It worked but I had no wifi. tried a few things to get it working and in trying to flash an XSA CSC (I think it was XSA) I got the Knox bit change. With no wifi I thought maybe the problem was the BUT-based CP needed changing. In trying to fix that, somehow I triggered Knox
I tried DL & Install of Omega 6 (it's a 4.3 - not ready to go KK yet) but although it completed nicely (so many ROM's got hidden or system errors in Odin) the phone didn't start. I tried installing Philz so I could run things from the extSDcard but an XSA wouldn't work nor would anything I had below MJ7. Last Phone Info view I had I still had a ZHU CP, even though AP and CSC were XSA-based.
Finally I got the MJ7 ROM from http://forum.xda-developers.com/sho...9005xxudmj7-pre-rooted-knox-free-odex-bl-free and it did the trick.
It's been a learning experience but I'd be happier if I knew for sure both what triggered the Knox bit (I was being very careful about it) and why some of the other ROM installs simply didn't work.
Resurrecting this one because I'm looking for info on flashing my 32G HK Note 3, but it came with KK pre-installed. So I'm not sure what differences I have to be aware of. Any tips?
For whoever still experiences issues with HK 32GB n9005 devices, After wasting half a day on that crap, i was able to flash N9005ZSUGOK2_N9005OZSGOK2_TGY from sammobile coupled with the PIT attached.
sm-n900
sm-900 and pit

[GUIDE] [OFFICIAL ROM] [GT-N5100] 4.4.2 Kitkat Update!

Hello everyone, Im new here and this is my first thread. Please forgive me if I make mistakes. And sorry, I got no screenshots.
Did you ever wish you had Android KitKat on your GT-N5100? Well wish no more! The Official Update has already been released to Korea and Poland! It shouldn't take long for it to reach to other countries.
But if you are impatient, you can flash it now via Odin! ☺
Notes:
Make sure you have at least 80%
Make sure you have a back up
Make sure you remove ALL signs of root (e.g. Xposed,Busybox etc.)
Make sure all the apps in your External SD is moved to your Internal Storage. (To avoid force closing problems)
Make sure you have USB Debugging Enabled in Settings>Developer Options>USB Debugging
BEFORE THE PROCEDURE MAKE SURE YOU MAKE A BACK UP BECAUSE THIS CAN SOFT BRICK YOUR DEVICE.I AM NOT RESPONSIBLE FOR ANYTHING YOU DO WITH YOUR PHONE/TABLET/PHABLET
LETS BEGIN!!!
Download the Firmware from the Post below
After that unzip it and you will see 2 files, just put your attention to the tar.md5 files
Install Odin3 (Links below)
Now you need to install Samsung Kies. (Link also Below)
After installing kies go to the Odin3 Folder, Right click on it and hit "Run as Administrator"
Now that your done with the PC's Part. Put your attention on your tablet and shutdown/Power Off
After that press Volume Down and Home for a few seconds until you get into a screen with a Warning, just press Volume Up to continue.
And after that connect your phone to your PC via USB and Odin should automatically detect it.
An ID:COM[Number] will show in a box on the upper right and then click on PDA and go to the directory of where you put the unziped firmware folder you downloaded from SamMobile. Select the tar.md5 file.
After that make sure you dont have re-partition checked. Double check if you need to and hit "START"
PLEASE DONT REMOVE YOUR PHONE UNTIL YOU SEE A "PASS" MESSAGE IN THE BOX.
After that it should reboot and you now have Android 4.4.2 Kitkat on your GT-N5100!
Good Luck!
Incase you get in a Boot Loop
Press Volume Up and Power button to get into Recovery and perform a Factory Reset (Data wipe) then Wipe Cache Partition and Reboot.
Enjoy!
Source: International Business Times
Hit that thanks button if this helped!
LINKS ADDED! YEY!
ROOTING GUIDE COMING SOON
TROUBLESHOOTING
If your PC doesnt recognize your device, try reinstalling drivers, and if you are stuck on Download Mode just press and hold the Power Button until it shuts down then press and hold it again to turn your device on!
Tested on a Note 8! Didnt brick the device and is working, just make a backup incase you screw up.
Wanna see the changes? Go here
LINKS!
LINKS
Firmware
Kies (After updating make sure you use Kies3)
Odin3
Don't want to download Kies? Download these USB Drivers instead.
Enjoy!
ROOTING GUIDE IS NOW HERE
Click here to root you Samsung Galaxy Note 8!
John Shenon Uy said:
ROOTING GUIDE IS NOW HERE
Click here to root you Samsung Galaxy Note 8!
Click to expand...
Click to collapse
Quick and noob question.
I have Note N5100 stock, it is still on 4.1.2 firmware, now i want to flash with odin official 4.4.2 kitkat on it. (from above post)
So question is, do i need to root it first so i can flash 4.4.2?
Thank you.
CowboyWorld said:
Quick and noob question.
I have Note N5100 stock, it is still on 4.1.2 firmware, now i want to flash with odin official 4.4.2 kitkat on it. (from above post)
So question is, do i need to root it first so i can flash 4.4.2?
Thank you.
Click to expand...
Click to collapse
I would not flash official 4.4.2 kitkat with odin, over kies or over ota. You will get kitkat bootloader with knox, no write permissions for your apps to sd card, no working rooting method which would not trigger knox and void your warranty.
The rooting method he linked does not work for Exynos 4412 devices. Read the comments to the original geohots post in s5 forum or at least the towelroot thread in this section.
Yulka said:
I would not flash official 4.4.2 kitkat with odin, over kies or over ota. You will get kitkat bootloader with knox, no write permissions for your apps to sd card, no working rooting method which would not trigger knox and void your warranty.
The rooting method he linked does not work for Exynos 4412 devices. Read the comments to the original geohots post in s5 forum or at least the towelroot thread in this section.
Click to expand...
Click to collapse
Yeah it doesn't work, use CF-Auto-Root. Works perfectly,but you will see SuperSU Force closing or in some cases, it is not installed to fix this, install/update SuperSU
If and onlyif it doesn't work, try again.
John Shenon Uy said:
Yeah it doesn't work, use CF-Auto-Root. Works perfectly,but you will see SuperSU Force closing or in some cases, it is not installed to fix this, install/update SuperSU
If and onlyif it doesn't work, try again.
Click to expand...
Click to collapse
I have done update to 4.4.2 with odin and with out root.
And there is no waranty woid or knox trigger.
So everything was OK. But i have downloaded Poland version of 4.4.2 N5100XXDND8 from samsung updates page.
thank U
Sorry for the newbie question but how can I efficiently and completely backup my device? Any apps/software I can use? I know that I can just make a copy of all my photos, videos, etc to my laptop but how about my apps and its data? Will they be deleted after flashing this firmware?
I've got a problem here .
My simcard doesn't work .
It keep saying emergency calls only
Sent from my GT-I8262 using XDA Free mobile app
excuse me sir do you have a mirror of this firmware link like 4shared or mediafire?
would you please update download link of firmware? its expired
thanks
After I flashed my GT-N5100 with Samsung's official firmware, it keeps crashing apps everytime... Why??
PS: I can't install Ten Million (10000000) game as well somehow.
---------- Post added at 07:36 PM ---------- Previous post was at 07:32 PM ----------
imaniacsz said:
excuse me sir do you have a mirror of this firmware link like 4shared or mediafire?
Click to expand...
Click to collapse
Try the official Firmwares: http://www.sammobile.com/firmwares/database/GT-N5100/
Thanks
efs problematic after flashing firmware N5100
HI, its my first post on xda and new to this world so i will try to be reasonable here.
i followed the steps mentioned in this thread except one, i.e. i didnt make a backup. Now my n5100 wont move beyond initial samsung logo and the recovery mode says "cannot mount / efs"
i also found a thread which makes some excellent points (see below), but i would still like to know if any of you tried this and had a similar problem. if so, did you find a DIY method
http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289

Galaxy s6 Edge Root (Most Variants)

This is a new Root method I made using @g.lewarne @mikeyinid for the Custom Kernel
---------------------------------------------------------
-----------Galaxy S6 Edge Root (Most Variants)----------
Only compatable with models: G925 F/I/S/K/L/T/W8
(Compatable with most S6 Edge with an unlocked bootloader via devolper options)
Disclamer I am not responsible for any damages.
Processed at your own risk!
----------------------------------------------------
Step 1- Extract this .ZIP
Step 2- Make Sure all drivers are installed
Step 3- Open Odin3_v3.10.6 as Admin
Step 4- Select AP/Bootloader and locate the file
named S6-UniKernel_v2-0002-ODIN.tar
<Once rebooted you should see a red text "Kernel is
not Seandroid inforcing" ignore it you should see
Super User installed, Transfer the TWRP Manager.apk>
Step 5- Install TWRP Manager.apk, ignore SD card fix
pop-up and a pop should be of BusyBox is required
download it and install it from the Play Store
Step 6- Go to the TWRP app and click on the three bar
menu icon and select Install Twrp, scroll down for
"Samsung Galaxy S6 Edge"
Step 7- Select "Recovery Version to Install"
select the version you want and once its finsihed
downloading/installing it will say "do you want
to reboot to recovery" or something like that then
you should be in TWRP
Step 8- Enjoy Flashing roms
Full disclosure,
if my understanding is correct, This method Will trip the Knox bit.
Do not try this method if you wish for your Knox status to remain intact.
instaling custom recovery trips knox, but who cares, even samsung doesnt(in india) still claimed warrenty even after triping knox. even went for a replacement.
Thailand also strict on a KNOX status when RMA..
Mischala said:
Full disclosure,
if my understanding is correct, This method Will trip the Knox bit.
Do not try this method if you wish for your Knox status to remain intact.
Click to expand...
Click to collapse
Yes
ps000000 said:
Thailand also strict on a KNOX status when RMA..
Click to expand...
Click to collapse
There are other Root methods, not sure if anyone has a non Knox tripping method try PingPong Root, or kingroot, they might be good in your scenario
sarvanan84 said:
instaling custom recovery trips knox, but who cares, even samsung doesnt(in india) still claimed warrenty even after triping knox. even went for a replacement.
Click to expand...
Click to collapse
I should move to India
Galaxy S6 Edge Root 5.1.1 (Most Variants)
Only compatable with models: G925 F/I/S/K/L/T/W8
Once rooted is it supposed to show the words custom and an unlock lock when booting up on the screen?
Is it compatible with G925 5.1.1?
flow78 said:
Is it compatible with G925 5.1.1?
Click to expand...
Click to collapse
Which varIant
Archangel said:
Once rooted is it supposed to show the words custom and an unlock lock when booting up on the screen?
Click to expand...
Click to collapse
Not enterily show what you are referencing
When you boot up the phone and see the giant Samsung Galaxy Edge letters,,,underneath that there is a lock icon that is unlocked and it says custom underneath that,,,is that what it is supposed to look like after rooting,,,,,reason I ask cause it used to have something like that on the boot splash screen when you have an unlocked bootloader. I have a Verizon S6 Edge and know that cant be.
JerryIsaMaster said:
Not enterily show what you are referencing
Click to expand...
Click to collapse
jerryisamaster said:
which variant
Click to expand...
Click to collapse
sm g925f 5.1.1
Archangel said:
When you boot up the phone and see the giant Samsung Galaxy Edge letters,,,underneath that there is a lock icon that is unlocked and it says custom underneath that,,,is that what it is supposed to look like after rooting,,,,,reason I ask cause it used to have something like that on the boot splash screen when you have an unlocked bootloader. I have a Verizon S6 Edge and know that cant be.
Click to expand...
Click to collapse
Verizon and AT&T always have looked boot loaders so this method is ineffective
flow78 said:
sm g925f 5.1.1
Click to expand...
Click to collapse
It should work
How about sm-g925r4 on 5.1.1?
Sent from my SM-G925R4 using Tapatalk
david.finch.79274 said:
How about sm-g925r4 on 5.1.1?
Sent from my SM-G925R4 using Tapatalk
Click to expand...
Click to collapse
I don't think so, feel free to try but you are doing it at you're own risk, I do not recommend it.
i have a problem after doing everything after the instructions, after the restart only shows the red text on left top corner and after that the logo on bottom, but after that both bottom led's (back and setting button) flash really fast and nothing else happens. i can tuch the screen it vibrates, but nothing else, no picture whatsoever.
Doesnt work for me on 925F.. Root works, but can't install TWRP. i get bootloop.

Downgrade to 4.4.4. from 5.1.1 (or 5.0.1) with security patch 2016-04-02

Hi,
Required to downgrade to 4.4.4 so one of my app will run.
Everytime i flash 4.4.4 with Odin, i got the error message like, SW Rev Check Fail.
Cannot find kitkat bootloader, either.
Fastboot won't connect to my phone, so i cannot unlock bootloader to get back to 4.4.4.
I called Samsung service center to downgrade, it won't offer the service, even paid one.
Big trouble, anybody can help, please?:crying:
godel.chen said:
Hi,
Required to downgrade to 4.4.4 so one of my app will run.
Everytime i flash 4.4.4 with Odin, i got the error message like, SW Rev Check Fail.
Cannot find kitkat bootloader, either.
Fastboot won't connect to my phone, so i cannot unlock bootloader to get back to 4.4.4.
I called Samsung service center to downgrade, it won't offer the service, even paid one.
Big trouble, anybody can help, please?:crying:
Click to expand...
Click to collapse
I believe once you upgrade to 5.1.1 (CJ05) bootloader, you cannot downgrade to 4.4.4 anymore.
godel.chen said:
Hi,
Required to downgrade to 4.4.4 so one of my app will run.
Everytime i flash 4.4.4 with Odin, i got the error message like, SW Rev Check Fail.
Cannot find kitkat bootloader, either.
Fastboot won't connect to my phone, so i cannot unlock bootloader to get back to 4.4.4.
I called Samsung service center to downgrade, it won't offer the service, even paid one.
Big trouble, anybody can help, please?:crying:
Click to expand...
Click to collapse
You can't, COJ5 locked bootloader, as far as I'm aware no one succeeded in bypassing that.
Also... use search ffs...
Thanks for all the reply, it looks i post the wrong board and cannot move or delete it, my apology, i will go looking for help at QA board instead. BTW, what's search for ffs? ffs? Sorry for question again and many thanks in advance.
Sent from my SM-N910U using XDA-Developers mobile app
You may want to consult urban dictionary to find out what 'ffs' means.
Otherwise, as others have stated, you cannot downgrade to 4.4 no longer (I don't believe custom Roms can do the trick either). Is the app in question a play store app pending an update? Seems a bit silly to downgrade the whole system for one app, even considering any potential benefit kitkat may bring..
Sent from my SM-N910U using Tapatalk
I have successfully downgradet my 910F from
PDA:N910FXXS1CPC5
CSC:N910FTMS1COI1
to
PDA:N910FXXU1ANK4
CSC:N910FTMS1ANK1
So how to:
Download FW from sammobile and latest Odin v3.10.7. In recovery wipe cash , wipe data/factory reset. Shutdown, remove w8 a bit inser battery back and boot up phone into download mode. In odin load FW first and after connect phone. Just press flash button and w8 till phone boot up . My knox stay 0x0
I don't mean this the way it might sound, i just dont know how else to word my question....but what makes this method different from all the others. Was the 5.1.1 firmware that you were on the latrat for n910F. I have been trying to find a way to downgrade my n910t since I bought it. How can I make it work on mine haha.
Vybramo said:
I have successfully downgradet my 910F from
PDA:N910FXXS1CPC5
CSC:N910FTMS1COI1
to
PDA:N910FXXU1ANK4
CSC:N910FTMS1ANK1
So how to:
Download FW from sammobile and latest Odin v3.10.7. In recovery wipe cash , wipe data/factory reset. Shutdown, remove w8 a bit inser battery back and boot up phone into download mode. In odin load FW first and after connect phone. Just press flash button and w8 till phone boot up . My knox stay 0x0
Click to expand...
Click to collapse
not work with N910 c
i have tried to down grade from
PDA:N910CXXS2CPB3
CSC:N910COJV2COK1
which has the same android security patch 3/2016 like you're fw
to
Kit kat N910CXXU1AOB1
but failed and the same error of locked bootloader appeared
Vybramo said:
I have successfully downgradet my 910F from
PDA:N910FXXS1CPC5
CSC:N910FTMS1COI1
to
PDA:N910FXXU1ANK4
CSC:N910FTMS1ANK1
So how to:
Download FW from sammobile and latest Odin v3.10.7. In recovery wipe cash , wipe data/factory reset. Shutdown, remove w8 a bit inser battery back and boot up phone into download mode. In odin load FW first and after connect phone. Just press flash button and w8 till phone boot up . My knox stay 0x0
Click to expand...
Click to collapse
I believe your bootloader is not locked.
Sent from my SM-N910C using XDA-Developers mobile app
Have someone done this on a N910U?
I've downgraded from MM to KK but GPS not working.
Inviato dal mio SM-N910F utilizzando Tapatalk

Categories

Resources