[ROOT] SGH-I467 ATT Note 8

LOCKxNXLOAD

Senior Member
Sep 26, 2013
62
7
0
totally not your fault man. All I know that could be holding me up would be that when i originally rooted i had to go back from mf2 to mf1. So i had to install the bootloader csc n what have you. When I went back to mf1 all i did was flash the stock mf1 tar.md5 nothing else. maybe with it being dirty it messed something up. I thought that since it was an ota to 4.4.2 that it would have replaced anything and then been stock 4.4.2. I may have to recover/flash the 4.4.2 cfig and start from scratch 4.4.2 again, but dont see how it would make a difference...


ALSO TRIED 4.5 KING ROOT GETS FARTHER THEN 4.1 STILL FAILS THOUGH. HEADS UP FOR ANYONE ELSE IT MIGHT WORK AS WELL.
JUST NOT FOR ME APPARENTLY!
 

dandroid7

Senior Member
May 26, 2013
437
406
0
I'm not aware of any 4.4.2 files being available to reflash it... but yeah, maybe something weird going on and a clean flash could get rid of the gremlins. If I can find any other ideas, I will let you know.
 

LOCKxNXLOAD

Senior Member
Sep 26, 2013
62
7
0
Someone earlier in the thread put a link to a captured ota. I should be able to flash it in recovery as long as its a signed file. it should still if being the same 4.4.2 allow it through....I think. I'm not a samsung person really vanilla is my flavor of choice. Honestly I'd be tempted to send it out if someone would be willing to try. In all honestly I don't care about the risks lol the things a flimsy plastic turd IMO.

---------- Post added at 10:21 PM ---------- Previous post was at 09:54 PM ----------

Never mind it was kernel source... Sol I guess.
 

dandroid7

Senior Member
May 26, 2013
437
406
0
For those still trying to gain root access using Kingroot... here is a link to a few different versions of "kingroot", a version of "kinguser" (their version of supersu), and a version of "purify" (their version of a memory manager). If it didn't work easily, it may still work with a bit more trial and error, as it did for me.

https://drive.google.com/file/d/0B3w-dFE5Q3FOeDVuYkk3Q0hIR2s/view?usp=sharing

Yesterday morning, i woke up to find that I had somehow lost root on my tablet... I tried to re-root using the previous process, and it no longer seemed to work. Soooo, I spent a good chunk of time figuring out how to get root back yesterday. The good news is, I got root back... the process however, was somewhat convoluted.

So I tried to find a step by step reproduce-able way to get root every time - and I was not successful at coming up with an exact process that works every time... I was however able to get rooted every time, but the process seemed to vary a bit each time... so trial and error seems to be the key here. I experimented for hours doing this... gaining root, uninstalling root, and retrying - all in the name of trying to help others figure out how to do it on their device.

So here is the basics of how I achieved root... DISCLAIMER - I TAKE NO RESPONSIBILITY FOR YOU, YOUR ACTIONS, OR THE FUNCTIONALITY OF YOUR DEVICE - BEFORE/DURING/OR AFTER YOU TRYING ANY OF THESE PROCESSES THAT I TRIED. THINGS CAN GO WRONG - YOU CAN END UP WITH PROBLEMS - A BRICKED TABLET, A DIVORCE, A DEAD DOG, OR HIT BY A NUCLEAR BLAST. ANY OF WHICH, I TAKE NO RESPONSIBILITY FOR. IF YOU PUSH THE BUTTONS, ITS YOUR RESPONSIBILITY.

Since there is no factory image for 4.4.2 on our device, proceed with caution... if something goes really wrong, you will have a paperweight. There is no Kies or Odin to save you... Also, my knox warranty void count shows as 1 and custom device status, so if you are worried about that be aware...

1) download all the files in the folder at the link above, extract them from the folder and put all the apk's on your device, but dont install them yet (doesn't matter internal/external memory)
2) Boot into stock recovery and wipe cache. reboot.
3) Install kingroot v4.0.1.237
4) open kingroot and try the rooting process. the device will likely reboot at around 18 to 25% or so... once the device reboots, open kingroot again and let it finish the rooting process. If it works - you should go buy lottery tickets, because you just got really lucky! If it doesn't work, proceed to the next step.
5) Install Purify. Run Purify process. Take notice after running the process - at the top of the app does it say root is achieved?? If not, return to step 4 and try rooting again. If that does not work...
6) Install kinguser. open kinguser, does it say you have root access? If not, try the prompt to repair root access (if it shows up)... if not, return to step 4, and try to root again. If no root, try step 5 again. If not, try step 6 again...
7) If still no root access, uninstall kingroot, and install one of the other versions of kingroot... try all of the above again. If still no root... uninstall all 3 apps and start over at step 2 using a different version of kingroot to start with.

I wish I could say there was a logical rhyme or reason for what works and what doesn't... but there didn't appear to be an exact process that works every time. Fortunately, I was able to get root if I tried long enough and tried different combinations of processes. Periodically clearing the cache from the stock recovery really seemed to help increase my odds of success when things weren't going well.

Occassionally the process landed me in a bootloop at the at&t screen... after holding the power button for an eternity, the device would power off - then I would reboot and it would boot normally.

Additionally, I tried on many occasions to swap "kinguser" with "supersu" using an app call "Super-Sume". Sometimes the process worked, and successfully removed kingroot, kinguser, and purify - while keeping root and installing Supersu... Other times the process removed the kinguser, kingroot, and purify - but I also lost root. I tried both the paid and free versions of Super-Sume, but the free version is the one that seemed to work best.

It's up to you if you want to go through all of this - it was tiresome... but if you really want root, maybe trying something like this might help you - maybe not. I also noticed that kinguser seems to sometimes have root access, sometimes not... so sometimes it was just a matter of opening one of the 3 apps and re-running a process or two and root would be restored... not sure why that happens - which is why i opted to use super-sume to remove kingroot once root was achieved. but we will see if i keep root now... if not, at least I know the process above seemed to work for me.
 
Last edited:
  • Like
Reactions: LOCKxNXLOAD

LOCKxNXLOAD

Senior Member
Sep 26, 2013
62
7
0
Tried through the steps earlier and was still unable to obtain root. I will continue to try as I was at least able to get further percentage wise. As well kingroot 4.0.1.237 isn't giving the option to attempt root. Immediately says no strategy so I had to start off with a different version. Anyone else having this issue?
 

kcour2006

Senior Member
Dec 17, 2007
113
11
0
Denver
I tried again and the kinroot app wont even attempt to root as well.
Oh well, if the other perdon was able to root maybe they can get root going faster with some dev help.

KC - ROOTED
 

dandroid7

Senior Member
May 26, 2013
437
406
0
Yeah, I had that happen numerous times as well... I'm not sure why. I did notice that once I wiped the cache in the stock recovery, sometimes that seemed to help the process.

I've rooted quite a few android devices in the past. The first time I used king root on this device, it was super simple... then I lost root for some reason after a while. Then when i tried to use king root again on the same device, it didn't work so simple, but I eventually got it after messing with it long enough. Makes no sense to me why it was so difficult the second time around.

There are a few more versions of Kingroot v4.1 out there... when I have time this evening I will post a link for you to try them also. The ones I have posted are the ones that seemed to work best for me, but who knows, maybe the other ones will work better for you.

Good luck.
 

LOCKxNXLOAD

Senior Member
Sep 26, 2013
62
7
0
I have all the versions saved up already lol. So no need unless you want to in order to help others. I've wiped cache gone through every step with every version and still nothing. I'm thinking I'm just not meant to have root man. I will continue though. I'm really hoping I'm just missing something I will inevitably get. I do appreciate all the help however!

---------- Post added at 08:46 AM ---------- Previous post was at 08:44 AM ----------

I tried again and the kinroot app wont even attempt to root as well.
Oh well, if the other perdon was able to root maybe they can get root going faster with some dev help.

KC - ROOTED
I build my roms, but I'm not much at this sorta thing. I'm working on breaking it down to see which strategies work and pulling it for maybe a designated for this device root method. It's slow going though so if anyone would like to chip in have at it.
 
  • Like
Reactions: dandroid7

huynhson

Member
Oct 24, 2012
18
2
0
Hello, I can not post on the developer forums yet, so I will post what I can here.

I was able to get root access to my Samsung ATT Note 8 (SGH-i467). See attached image.

Thank you;

lyriquidperfection: for the packing tools. http://forum.xda-developers.com/show....php?t=2411243
globula_neagra: for the comments on system.img. http://forum.xda-developers.com/show....php?t=1971249
SkipKelley: for starting me off. http://forum.xda-developers.com/show....php?t=2385265
The XDA Forums: for being available.
chainfire: for obvious reasons. http://www.chainfire.eu/

I will try to put together a complete how to when I can. For now I will link to the image files I created.

DO THIS AT YOUR OWN RISK! I DO NOT TAKE ANY RESPONSIBILITY FOR YOUR DEVICE NOT WORKING.

Here we go.

1. Download the i467 firmware from http://www.sammobile.com
1a. Extract the main zip file you downloaded. Leave the .tar.md5 files intact. They are the files you select with Odin in steps six (6) and nine (9).

2. Download Odin 3.07 from http://forum.xda-developers.com/show....php?t=1738841
2a. Extract and launch Odin.

3. Download the pre-rooted I467UCAMF1 images from SAMSUNG-SGH-I467I467UCAMF1-ROOT.tar
3a. Do not extract or modify this file.

4. Do a factory reset of the device either in system settings or using recovery (volume up). Yes, I have found you must do this.
5. Boot into download mode. (Home + Volume Down + Power)

Step 6 is only required if you accepted the OTA "CAMF2".
6. Use Odin to flash all four files downloaded in step 1. BOOTLOADER, CODE, MODEM and CSC files.
6a. Let the device finish install and boot.
6b. Boot into download mode. (Home + Volume Down + Power)

This is the fun part.
7. Select PDA in Odin and select the file downloaded in step 3. Make sure all other files are not checked. Flash... Odin will say it failed. Yes, don't worry, recovery is still there.
8. Reboot into download mode (Home + Volume Down + Power)
9. Using Odin only flash the BOOTLOADER, MODEM, and CSC from step 1. Do not flash the CODE file or the modified image. In other words, leave PDA unchecked in Odin.
10. Let the device install and reboot.

You should now be able to run SuperSU.

If you want to update to OTA CAMF2 then follow these steps BEFORE DOING ANYTHING ELSE;

Thanks to DanMc85 and others for testing. Also, usernamenotfound wrote instructions in the next post, thank you.

1. Start SuperSU and in the settings enable Survival mode.

2. Connect to a Wifi network. (Thanks aTt)

3. Go to system Settings and select About Device at the bottom of the list.

4. Select Software update on the right.

5. Go through the update process and the device will reboot. You should be at version CAMF2.

[EDIT]

Bootloader = BOOTLOADER...tar.md5
PDA = CODE...tar.md5 - Don't select this in step nine (9). Leave blank.
PHONE = MODEM...tar.md5
CSC = CSC...tar.md5
i do like direction but when put the CSC in.. it said wrong parametter... anyway else to root it. Thanks bro
 

LOCKxNXLOAD

Senior Member
Sep 26, 2013
62
7
0
Okay so no luck finding a sure fire successfull root for the sgh i467. Every attempt using king root has failed. I did finally achieve root using 360root though. It's entirely in Chinese but just keep clicking around and it's easy to figure out. I have though not been able to change my root manager (ie, supersu/superuser) so if anyone can help out let me know.

Here's the link to my version of 360root I modified to work almost with certainty not 100 percent though. https://drive.google.com/folder/d/0B45Loy1X4-5lNFFhVmNfc2EyNU0/edit

Thanks everyone for the help along the way!
 

Attachments

tafkam4055

New member
Jul 24, 2011
3
1
0
I've read a bunch of the posts...I think the answer is no, just figured I'd ask though, is there anyway to get a ROM on this thing?
Really not a fan of Samsung's skin.

As an alternative, is there anyway (with an app I guess) to replace the Notification bar?
 

LOCKxNXLOAD

Senior Member
Sep 26, 2013
62
7
0
Sadly no. There isn't a way to install a rom on the device as it has a locked boot loader. I can tho suggest if you have obtained root or use the exposed framework and theme the device itself with wanam. If you have root simply look up here for the exposed module. Everything else can be accessed through the apk http://repo.xposed.info/module/de.robv.android.xposed.installer

---------- Post added at 02:20 AM ---------- Previous post was at 02:18 AM ----------

Did you try my provided method? Simply reboot into recovery wipe cache/dalvik. Once rebooted install the app and try it out. May take a few tries but I was successful over and over.
 
Last edited:

tafkam4055

New member
Jul 24, 2011
3
1
0
Thanks so much for getting back to me. I'm going to try your root method tonight.

Hopefully, I can wrap my head around xposed. This tablet is great, I just can't stand the Samsung UI.
 
  • Like
Reactions: LOCKxNXLOAD

LOCKxNXLOAD

Senior Member
Sep 26, 2013
62
7
0
It's no problem! Some stuff with the wanam module doesn't work but most will. It doesn't change the layout much but at least you can make it prettier lol
 

serverm07

New member
Nov 28, 2015
2
0
0
Hey guys,

Thanks a lot for all of the hard work and putting everything together. I really appreciate it since I'm not anywhere as tech savvy as some of you guys. I'm trying to back up the OS of the device before I try to root in case something goes wrong, I found "simple adb back up" and have read the directions quite a few times and tried to follow the steps. When I try to use it, cmd tells me "adb: unable to connect for backup". I'm assuming I either messed up the path or it's lacking some kind of permission. I tried two different usb chords to connect as well. I have enabled developer options and USB debugging in the tablet itself. I have tried adding the path under my pc > environment variable and point it to the adb. I'm guessing I'm screwing up somewhere in this step, if anyone could please help me out, I would really appreciate it. I just don't really have any experience with code so don't know what I'm doing wrong tbh. I have tried re-installing it as well. Almost tempted to just say screw it and try the root without backup :p. Also should I be following directions from the OP to root or should I be trying the kingroot? Saw someone make a post saying that worked.