Related
This Thread is a W.i.p...
Please PM me for any changes that needs to be made here. Or anything you can think of or any info that needs to be added ...
This tutorial for only those user, who recently updated their device with the Android 4.3 Jelly Bean I317UCUBMK6 firmware. Cf-Auto-root is one of the easiest and fastest way to root Samsung devices, it does nothing but install and enable SuperSU on your system, so apps can gain root access. Rooting has lots of benefits, after rooting your device you can install lots free rooted app on your device, install Custom ROMS etc.
---WARNING!!!!---
Your warranty is void if you follow the given instructions in this guide!!!!!
SOME SMALL REQUIREMENTS REQUIRED!!!!
Please Read about what your doing to your device if your new at this!!!!!
Make sure you understand how Android works.
Knowledge of basic flashing rules is something good to know!!
Using Custom Rom's, Recoveries, Odin, Etc..
Reading/Searching is your friend when doing anything to your device...
Before following the below Mention guide, It’s always recommended to follow the requirements to stay safe.
Click to expand...
Click to collapse
1. BACKUP YOUR ANDROID DATA
Make a Full Backup of your Android Apps, SMS, Contacts, Call Logs, Bookmarks. This one is one of the most important step that you have to follow, as we don’t want anyone losing their personal data or apps. For help on Backup and Restore check out the below mention guides.
[Guide] Backing up your data basics. Go >>[HERE]<<
Titanium Backup
Titanium Backup is the most powerful backup tool on Android, and then some.
Rom Toolbox
ROM Toolbox is THE MUST HAVE APP for every root user. Get ROM Toolbox Pro to unlock all the features!
2. INSTALL GALAXY NOTE 2 DRIVERS
You need these drivers to connect your device with the computer to follow this guide. Without these USB drivers you can’t connect your device to the PC, first download and install these drivers on your system.
[DOWNLOAD ANDROID USB DRIVERS]
3. ENABLE USB DEBUGGING MODE
Now you need to enable USB debugging mode. Without enabling USB debugging mode on your device you can’t start the root, Custom ROM or Unlock process.
HOW TO ENABLE USB DEBUGGING MODE ON ANDROID DEVICES
Enable-USB-Debugging
Go to setting, General tab, Developers Options.
(If no developers options visible. Then go to About Device, then scroll down to Build number and click it 7-times to have the developer options come up)
4. CHARGE YOU ANDROID
If your device switched off during this process, it could damage or brick the device. Make sure that your Android battery is full charge or near about 50-70% battery level.
How To Update Galaxy i317 via Kies
Make sure you have stable internet connection on your computer.
Now download and install>>[Samsung Kies]<<on your computer.
Turn on your device (if it off) and then connect it to computer with USB cable.
Run Samsung Kies and wait for it to detect your device.
You should see a New Firmware Upgrade is available at Samsung Kies home screen.
Press the Firmware Upgrade button to proceed.
Follow on screen instruction and soon you will see your device running upgrade and reboot automatically. Once done, you can disconnect your device from computer.
Again! If you see “This is the latest firmware” in Samsung Kies, then your device yet to receive the latest update on Kies. Its good time to go for manual update instruction that located below.
Part:1
ROOT GALAXY NOTE 2 AT&T SGH-I317 RUNNING ON ANDROID 4.3
Step 1. Download the Cf-Auto-Root Package for Galaxy Note 2 >>[HERE]<< and extract the folder on your desktop and you will get the CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 file.
Step 2. Download the ODIN flash tool >>[HERE]<< and extract the folder on your desktop. You need this tool to flash the root package on your device.
Step 3. Now turn off you device and wait for few seconds. Then boot the device into Download Mode by pressing and holding Volume Down, Home and Power buttons together until a construction Android robot icon with a warning triangle appears on screen. Now press the Volume Up button to enter Download Mode.
Step 4. Now your Note is in download mode, Connect your device to the PC with USB cable.
Step 5. Launch Odin on the computer and the ID: COM box of your ODIN Screen will turn to light blue with the COM port number. This means your device is connected successfully with the app.
Step 6. In Odin, click the PDA button and select the CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 file (Same File that you extracted on your desktop on Step 1)
ODIN Screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, ensure that the check boxes “Auto Reboot”, “F. Reset Time” and “PDA” are the only check boxes checked and the rest are not. And Make sure re-partition is NOT ticked on the ODIN application
Step 7. Click start and wait for some time to run the root process.
Once the process is finished on your device you will see the a PASS message with green background on the ODIN application
Now you can disconnect your device from the computer and your device is rooted now....
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Part:2
Now for flashing a New Custom Rom Steps
If you have done the above^^^^^^^ steps and you've successfully Rooted . Then proceed to Step 1
1. First make sure you have a custom [>>[Recovery]<<] installed.
You can find the Recovery files here:
http://techerrata.com/file/twrp2/t0lteatt/openrecovery-twrp-2.6.3.1-t0lteatt.img.tar Flash this via Odin
http://techerrata.com/file/twrp2/t0lteatt/openrecovery-twrp-2.6.3.1-t0lteatt.zip
2. Then choose your Rom of choice to install.
For those looking for stock 4.3 pre-rooted firmware go>>[HERE]<< Thanks to Zen Arcade
For All Custom Roms look >>[HERE]<< and also >>[HERE]<< for the Original Development Section.
3. After choosing your Rom. You can reboot into recovery now.
Recovery Instructions Below
a. Wipe your system= Factory Data Reset
b. (Goto Advance) Wipe your cache/dalvik, Data, System, Internal 3x
c. Wipe Internal storage for a clean install. [BACK UP your stuff you want before wiping Internal!!!!!]
d. Locate Rom file on your ext SD card, flash Rom, let it finish. Should be about 5 minutes or less.
After you reboot let the Rom settle for about 5-10 minutes minimum. Before setting up your device.[Google Account]
Fix Boot Loop Issue On i317.
If your Note2 is stuck at booting animation for more than 10 minutes after Step 7 Part1 then follow below instructions:
Go to recovery mode. To do so, press and hold the Volume Up, Home and Power buttons together.
Now perform Wipe data/Factory Reset and Wipe Cache Partition task before selecting reboot system now function. In recovery mode wipe cache/dalvik one last time before reboot.
Please note, performing wiping task will erase your device internal memory data and not external SD card data.
That’s it! Let us know about your latest Android 4.3 Jelly Bean experience.
Click to expand...
Click to collapse
To downgrade 4.3 I317UCUBMJ4 bootloader...( ATT only for now)
Thanx to @Seanscreams
Go here for instructions and >>[LINK]<<
For some FAQ answers go >>[HERE]<<
Thank you this^^^^^^Zen Arcade
Donations
Donation from kdiff 0GX436403M4020453
Mine.....
Here is theOne Click Odin File...
Please Note The above^^^^^^ file does include Knox security!!!
Its the original Leak 4.3 firmware
Instructions for using the above file.
Follow Part 1 from above. Steps 3-5
Step 3. Now turn off you device and wait for few seconds. Then boot the device into Download Mode by pressing and holding Volume Down, Home and Power buttons together until a construction Android robot icon with a warning triangle appears on screen. Now press the Volume Up button to enter Download Mode.
Step 4. Now your Note is in download mode, Connect your device to the PC with USB cable.
Step 5. Launch Odin File above on the computer and the ID: COM box of your ODIN Screen will turn to light blue with the COM port number. This means your device is connected successfully with the app.
Click to expand...
Click to collapse
Then hit start Odin will do it's thing, and then you'll have the 4.3 Bootloader.
Reserved...
And 1 more just in case...
Well done.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
mindmajick said:
Well done.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Thanx man appreciate it!
Wrong Thread, please ignore me
Geeve
mindmajick said:
Well done.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Awesome! This should end some of the questions that are.......um......repeated? maybe? Nice work!
dmxinc said:
Awesome! This should end some of the questions that are.......um......repeated? maybe? Nice work!
Click to expand...
Click to collapse
Nah.. lol. But now I can yell at people and tell them they haven't searched hard enough
Sent from my SAMSUNG-SGH-I317 using Tapatalk
geeve420 said:
Thank you so much for this!! I was wondering just today if this was possible yet. It is nice to see it all in one place!
So does triangle away work to clear the binary? I know knox is undoable as of now, but wondering about the other counters.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Thanx:thumbup:
As far as the triangle away working, I actually haven't ran it in awhile. Flashing much all the time.
But last time I used it, was on my TMO GN2 after I Odin back to stock.
But I'm getting ready to clean out my phone soon. So I'll test it and see if it works...
Looks great - nice job!
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Exelent contribution...
Enviado desde mi GT-N7105 mediante Tapatalk
mataflakitas said:
Exelent contribution...
Enviado desde mi GT-N7105 mediante Tapatalk
Click to expand...
Click to collapse
Thanx bro...:thumbup:
SENT FROM MY SAMMY TO YOUR EYES USING TAPTALK?
Nice guide bro well done ?
Sent from my SGH-I317 using XDA Premium 4 mobile app
Thanks for the great step by step! I have one question just for clarification before proceeding on my wifes phone. Can I flash any rom or am I stuck with only 4.3 based roms? My wife absolutely hates all changes in the stock 4.3 update and wants back to the 4.1 she was on before.
scottyb0721 said:
Thanks for the great step by step! I have one question just for clarification before proceeding on my wifes phone. Can I flash any rom or am I stuck with only 4.3 based roms? My wife absolutely hates all changes in the stock 4.3 update and wants back to the 4.1 she was on before.
Click to expand...
Click to collapse
same question. plus if i do this, would it change my knox status?
scottyb0721 said:
Thanks for the great step by step! I have one question just for clarification before proceeding on my wifes phone. Can I flash any rom or am I stuck with only 4.3 based roms? My wife absolutely hates all changes in the stock 4.3 update and wants back to the 4.1 she was on before.
Click to expand...
Click to collapse
Any rom.
xuanphucn said:
same question. plus if i do this, would it change my knox status?
Click to expand...
Click to collapse
It won't reset it to 0x0 if that's what you are asking.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
mindmajick said:
Any rom.
It won't reset it to 0x0 if that's what you are asking.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
my knox status is 0x0. would it still remain 0x0 if I do this?
xuanphucn said:
my knox status is 0x0. would it still remain 0x0 if I do this?
Click to expand...
Click to collapse
If you root or install custom recovery or do practically anything (if you are on stock 4.3)... Knox will be tripped. No takebacks.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
mindmajick said:
If you root or install custom recovery or do practically anything (if you are on stock 4.3)... Knox will be tripped. No takebacks.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
thats unfortunate
[Q] Rooted SPH-L710 with ODIN & CF-Auto-Root, Root Checker shows NOT rooted. HELP?!
I have had my Sprint Samsung Galaxy S3 for about a year now, and finally decided to give root access a try on the phone. I followed all of the step-by-steps tutorial, that Chainfire posted on his ([SPH-L710] CF-Auto-Root) thread, and have run into an issue. ODIN shows that the rooting procedure has passed, and the red android dude popped up, and the phone rebooted. Anytime I turn on my device, I immediately receive the notification that "unfortunately, SuperSU has stopped working". And running the app "root checker" returns the message "sorry! this device does not have proper root access". I went into download mode, and the flash counter shows that I have 1 custom rom/binary, whatever its called, and that my phone has the custom rom/binary status. I did some researching on the forums and threads, and it would seem that there's no clear cut way to fix this issue; given my phone's specific state. I don't want to brick my phone, so I need an experts solution! Thanks a million in advance!
If you want to leave root alone, you can reflash stock 4.4.2 is in Odin. But if you want to try to fix root you can flash a custom recovery is in Odin so you can flash an update to superuser using the custom recovery
Reply
thenexusgeneration said:
If you want to leave root alone, you can reflash stock 4.4.2 is in Odin. But if you want to try to fix root you can flash a custom recovery is in Odin so you can flash an update to superuser using the custom recovery
Click to expand...
Click to collapse
I would like the keep the phone rooted (which it has an issue with)....so as for fixing the root, by flashing a custom recovery....where do I find the custom recovery, and how exactly do I do this in ODIN, to specifically update superuser?
**NOTE: I downloaded a different superuser app on the google play store, (which will obviously not be saved/stored to system/app, like chainfire's SuperSU app is) and when I opened the Superuser app, it returns a message "SuperSU binary is out of date". I'm not sure what this means exactly, but maybe it might mean something to you, haha.
Have you tried this:
Go to the Google play store and find supersu. It should give you the option to "update" (versus "install")
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
Have you tried this:
Go to the Google play store and find supersu. It should give you the option to "update" (versus "install")
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
All it says is" open". That's the only option on the Google play store.
Jayhawker69 said:
I would like the keep the phone rooted (which it has an issue with)....so as for fixing the root, by flashing a custom recovery....where do I find the custom recovery, and how exactly do I do this in ODIN, to specifically update superuser?
**NOTE: I downloaded a different superuser app on the google play store, (which will obviously not be saved/stored to system/app, like chainfire's SuperSU app is) and when I opened the Superuser app, it returns a message "SuperSU binary is out of date". I'm not sure what this means exactly, but maybe it might mean something to you, haha.
Click to expand...
Click to collapse
If you're looking for;
Odin
http://odindownload.com/
Philz
http://d-h.st/users/philz_touch/?fld_id=25216#files
SuperSU (zip)
http://download.chainfire.eu/396/SuperSU/
But as suggested try opening supersu first. Mine would fc, so I just flashed the supersu file above, from philz recovery.
I would also suggest Uninstall in the other su app. They never played well together (for me)
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Jessooca said:
Open it and if prompted select normal if it asks Normal or twrp/recovery
Click to expand...
Click to collapse
Any time I try to open it, it force closes with the message "unfortunately, SuperSU has stopped."
Reply
Everytime I try to flash the twrp recovery, windows error reports pops up and says "ODIN communicator has stopped working and needs to close." I have noooo idea. Why is it doing this! I have the worst luck
If you're ND8 or NDC bootloader, the only completely working custom recovery is the very latest Philz Touch Recovery.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Thanks a million!!
roirraW "edor" ehT said:
If you're ND8 or NDC bootloader, the only completely working custom recovery is the very latest Philz Touch Recovery.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
roirraW "edor" ehT....THANKS A MILLION!! I have successfully in ODIN, flashed Philz Touch Recovery onto my S3. I booted into recovery, went in Philz settings, and clicked on the "re-root" option. I rebooted the device into the main system/shell, ran root checker to verify root status.....AND VOILA! ROOT STATUS GRANTED, BISH! I downloaded SuperSU from the play store, and everything seems to be running like butter. Consider this thread CLOSED!
Cheers from Lawrence, Kansas!,
-Brett
Jessooca said:
restart your computer and redownload odin
Everytime I try to flash the twrp recovery, windows error reports pops up and says "ODIN communicator has stopped working and needs to close." I have noooo idea. Why is it doing this! I have the worst luck
Click to expand...
Click to collapse
[/QUOTE]
Thanks for your help as well, much appreciated.
You're welcome and cheers right back from Columbus, Ohio. ☺
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
I need help toooo!
i've been having the same issue! thank you for working it out. i really want to complete the root, but im having trouble.
I'm very new to this stuff and I don't understand some of the instrutions.
could someone made make a clear cut instruction on how to do this?
I have an SPH-L710
I used Odin with CF- Auto Root.
When I try to open SuperSU, I get, "Unfortunately, Supersu has stopped." and I can't update it in Play. Just like OP.
I'm unfamiliar with recoveries and how to install them. I have the latest philz touch and SuperSu Zips on my computer ready to go. I have odin 3.07.
If Jessooca could make a clear cut instruction that would be awesome. Or anyone really..I just need some help.
Oh, and my computer won't recognize my phone. It did for a moment, but It hasn't been working for the past hour.
thank you!
thank you! that worked like a charm. however, i really wanted some free tethering, but it looks like kitkat won't allow FoxFi to do it! a pop up comes through about subscribing to the service. I installed SlimKat, and I hate it. It's fast and I can do the free tethering, but it's so ugly. I want to go back to my rooted kitkat. What should I do?
I don't think i made a correct back up. i thought i did, but i guess i didn't.
I'm downloading the official ROM for my SPH-L710 right now.
How can I return to a normal rooted kitkat?:good:
Kalen_Christian said:
thank you! that worked like a charm. however, i really wanted some free tethering, but it looks like kitkat won't allow FoxFi to do it! a pop up comes through about subscribing to the service. I installed SlimKat, and I hate it. It's fast and I can do the free tethering, but it's so ugly. I want to go back to my rooted kitkat. What should I do?
I don't think i made a correct back up. i thought i did, but i guess i didn't.
I'm downloading the official ROM for my SPH-L710 right now.
How can I return to a normal rooted kitkat?:good:
Click to expand...
Click to collapse
You might want to check in philz for any backups. If you have 1 it's easy to reinstall. If not, then you would have to flash your stock tar in Odin. Then, flash philz and then root. The more you do it the easier it gets. But, make sure that you are not downgrading by trying to flash an older stock tar. Downgrading your boot loader will cause a hard brick...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
You might want to check in philz for any backups. If you have 1 it's easy to reinstall. If not, then you would have to flash your stock tar in Odin. Then, flash philz and then root. The more you do it the easier it gets. But, make sure that you are not downgrading by trying to flash an older stock tar. Downgrading your boot loader will cause a hard brick...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
I checked Philz out very thoroughly and I don't think I did it correctly. So, I have to put a fresh 4.4.2 on. When I do want to creat a backup for recovery, What app should I use? Also, What are the main apps for superusers? I don't want to download a bunch of stuff I don't really need.
Thanks
**proper way to fix your problem!!**
Kalen_Christian said:
i've been having the same issue! thank you for working it out. i really want to complete the root, but im having trouble.
I'm very new to this stuff and I don't understand some of the instrutions.
could someone made make a clear cut instruction on how to do this?
I have an SPH-L710
I used Odin with CF- Auto Root.
When I try to open SuperSU, I get, "Unfortunately, Supersu has stopped." and I can't update it in Play. Just like OP.
I'm unfamiliar with recoveries and how to install them. I have the latest philz touch and SuperSu Zips on my computer ready to go. I have odin 3.07.
If Jessooca could make a clear cut instruction that would be awesome. Or anyone really..I just need some help.
Oh, and my computer won't recognize my phone. It did for a moment, but It hasn't been working for the past hour.
Click to expand...
Click to collapse
Ok, first off....no offense to the poster 'Jessooca', but the steps she has posted to solve your issue are in part, slightly incorrect and misguiding. The following steps are *EXACTLY* how you should proceed, in order to fix the problem/issue you are having (the EXACT same issue I dealt with for the past two days) :
Step One:
IF you haven't done so already, download the Samsung Galaxy S3 USB drivers from the following link. This should solve your connectivity problem. Following the link below, scroll down just a little bit, and click on the downloads tab located just to the right of the 'Manuals' tab. Click on the blue box that says "EXE", and this should get the proper driver downloaded for your Sprint Samsung Galaxy S3. And obviously, install the downloaded driver after it completes the download.
Link:
http://www.samsung.com/us/support/owners/product/SPH-L710MBBSPR?CID=AFL-hq-mul-0813-11000279#
Step Two:
I know that you have stated that you have already downloaded the 'Philz Touch Recovery'.zip file....but there is a chance you may not have downloaded the proper file for your specific and exact handset. So, here is the link for 'Philz Touch Recovery' that you should download and use for this process. It should be a direct link for the download file. I'll post a second link that you should only use as an alternative, in the event that the first link does not work. IF the first link didn't work, then make sure you download the most recently uploaded version of the Philz touch recovery from the alternative link; should be Sun, July 6th...and also be sure to click on the download link (there's two separate links) titled "philz_touch_6.48.4-d2lte.tar.md5"...as it will be much easier to work with than the .zip file.
Link One:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5
Alternative Link:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Step Three:
Now that we have the proper 'Philz Touch Recovery' file downloaded, you will need to download a different version of ODIN, as the 3.07 version you have will not suit our needs for this procedure. The link for the proper version of ODIN you will need is posted directly below. Download, extract it, and put the extracted folder somewhere on your computer that is handy or easy to find later. I'd suggest making a folder on your desktop from the very start of this procedure, and name it 'SPH-L710 Root Files', or w/e works best for you. Save all the files, or move all of the files you might have already downloaded at this point into that folder. Always nice to be organized and shizzz.
Link:
http://forum.xda-developers.com/attachment.php?attachmentid=581913
Step Four:
Alright, were getting closer to being done with this whole ordeal. Follow the link I have posted below, for the proper instructions on how to flash 'Philz Touch Recovery' in Odin to your device (the version of Odin we just downloaded from step three...obvi). Reading the instructions, you'll notice that it mentions that auto-reboot into recovery mode may not work properly after the file is flashed in Odin. This actually happened to myself....and seeing as how we have had the exact same problem with rooting our phones, I would suggest from the start, to uncheck the auto reboot option in Odin, and then manually boot into recovery mode after Odin successfully flashes the file to your phone. If you take my advice, and follow what I just said, your phone will still be in download mode after Odin flashes the file...assuming Odin says that the file successfully flashed ("PASS!"). From here, you will unplug your phone from your USB cord.....and now we will boot into the recovery file/mode we just flashed. To do this, HOLD down in this order: the Volume Up button + the Home key + the Power Button....continue to hold all 3 of these buttons down until the phone enters into recovery mode...you will be able to tell when you are in recovery.
Link:
http://forum.xda-developers.com/showpost.php?p=39433857&postcount=4
Step Five:
Ok, so hopefully if you did everything right to this point, and some other unforeseen issue has not arisen, you should be in Philz Touch Recovery Mode. Click on "PhilZ Settings" or "Advanced" , I can't remember for sure which one it is....but I'm almost positive it's in "PhilZ Settings"...click that option first. Within this settings menu, click on the option titled "Re-root" and click yes to proceed. After this is done, go back to the main menu and click on the "Reboot system/device" option on the very top.
Step Six:
Your phone should now boot up normally into your phones operating system/shell. Go to the Google Play store and search for and download an app called "Root Checker". Open the Root Checker app and click on the verify button. If everything worked properly, and if baby raptor Jesus loves you, the Root Checker will return the result that your phone has been properly rooted and you have root access/privileges. Now, go back to Google Play Store and download the "SuperSU" app....if it isn't already still on your phone (I had to re-download it). Open SuperSU from your apps menu/drawer and it might ask you to update the SuperSU binaries...mine did....and click on the normal method option, instead of the recommended option for HTC devices. SuperSU should update binary and your problems should all be melted away like butter by now.
** THIS IS THE EXACT SOLUTION(S) I TOOK TO FIX OUR SAME PROBLEM. I CAN'T GUARANTEE IT WILL WORK THE SAME FOR YOU, FOR WHATEVER REASON OR CIRCUMSTANCE THAT MIGHT BE. GOOD LUCK, YOU'LL DO GREAT KID :laugh::good:**
Kalen_Christian said:
I checked Philz out very thoroughly and I don't think I did it correctly. So, I have to put a fresh 4.4.2 on. When I do want to creat a backup for recovery, What app should I use? Also, What are the main apps for superusers? I don't want to download a bunch of stuff I don't really need.
Thanks
Click to expand...
Click to collapse
You would use philz recovery to make your backup. My apps that use root would be things like titanium backup, clean master, busy box. By going to the playstore and doing a search for root, you'll find apps that don't need root access but perform better when they have it...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Check this out !!!!
Jayhawker69 said:
Ok, first off....no offense to the poster 'Jessooca', but the steps she has posted to solve your issue are in part, slightly incorrect and misguiding. The following steps are *EXACTLY* how you should proceed, in order to fix the problem/issue you are having (the EXACT same issue I dealt with for the past two days) :
Step One:
IF you haven't done so already, download the Samsung Galaxy S3 USB drivers from the following link. This should solve your connectivity problem. Following the link below, scroll down just a little bit, and click on the downloads tab located just to the right of the 'Manuals' tab. Click on the blue box that says "EXE", and this should get the proper driver downloaded for your Sprint Samsung Galaxy S3. And obviously, install the downloaded driver after it completes the download.
Link:
http://www.samsung.com/us/support/owners/product/SPH-L710MBBSPR?CID=AFL-hq-mul-0813-11000279#
Step Two:
I know that you have stated that you have already downloaded the 'Philz Touch Recovery'.zip file....but there is a chance you may not have downloaded the proper file for your specific and exact handset. So, here is the link for 'Philz Touch Recovery' that you should download and use for this process. It should be a direct link for the download file. I'll post a second link that you should only use as an alternative, in the event that the first link does not work. IF the first link didn't work, then make sure you download the most recently uploaded version of the Philz touch recovery from the alternative link; should be Sun, July 6th...and also be sure to click on the download link (there's two separate links) titled "philz_touch_6.48.4-d2lte.tar.md5"...as it will be much easier to work with than the .zip file.
Link One:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5
Alternative Link:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Step Three:
Now that we have the proper 'Philz Touch Recovery' file downloaded, you will need to download a different version of ODIN, as the 3.07 version you have will not suit our needs for this procedure. The link for the proper version of ODIN you will need is posted directly below. Download, extract it, and put the extracted folder somewhere on your computer that is handy or easy to find later. I'd suggest making a folder on your desktop from the very start of this procedure, and name it 'SPH-L710 Root Files', or w/e works best for you. Save all the files, or move all of the files you might have already downloaded at this point into that folder. Always nice to be organized and shizzz.
Link:
http://forum.xda-developers.com/attachment.php?attachmentid=581913
Step Four:
Alright, were getting closer to being done with this whole ordeal. Follow the link I have posted below, for the proper instructions on how to flash 'Philz Touch Recovery' in Odin to your device (the version of Odin we just downloaded from step three...obvi). Reading the instructions, you'll notice that it mentions that auto-reboot into recovery mode may not work properly after the file is flashed in Odin. This actually happened to myself....and seeing as how we have had the exact same problem with rooting our phones, I would suggest from the start, to uncheck the auto reboot option in Odin, and then manually boot into recovery mode after Odin successfully flashes the file to your phone. If you take my advice, and follow what I just said, your phone will still be in download mode after Odin flashes the file...assuming Odin says that the file successfully flashed ("PASS!"). From here, you will unplug your phone from your USB cord.....and now we will boot into the recovery file/mode we just flashed. To do this, HOLD down in this order: the Volume Up button + the Home key + the Power Button....continue to hold all 3 of these buttons down until the phone enters into recovery mode...you will be able to tell when you are in recovery.
Link:
http://forum.xda-developers.com/showpost.php?p=39433857&postcount=4
Step Five:
Ok, so hopefully if you did everything right to this point, and some other unforeseen issue has not arisen, you should be in Philz Touch Recovery Mode. Click on "PhilZ Settings" or "Advanced" , I can't remember for sure which one it is....but I'm almost positive it's in "PhilZ Settings"...click that option first. Within this settings menu, click on the option titled "Re-root" and click yes to proceed. After this is done, go back to the main menu and click on the "Reboot system/device" option on the very top.
Step Six:
Your phone should now boot up normally into your phones operating system/shell. Go to the Google Play store and search for and download an app called "Root Checker". Open the Root Checker app and click on the verify button. If everything worked properly, and if baby raptor Jesus loves you, the Root Checker will return the result that your phone has been properly rooted and you have root access/privileges. Now, go back to Google Play Store and download the "SuperSU" app....if it isn't already still on your phone (I had to re-download it). Open SuperSU from your apps menu/drawer and it might ask you to update the SuperSU binaries...mine did....and click on the normal method option, instead of the recommended option for HTC devices. SuperSU should update binary and your problems should all be melted away like butter by now.
** THIS IS THE EXACT SOLUTION(S) I TOOK TO FIX OUR SAME PROBLEM. I CAN'T GUARANTEE IT WILL WORK THE SAME FOR YOU, FOR WHATEVER REASON OR CIRCUMSTANCE THAT MIGHT BE. GOOD LUCK, YOU'LL DO GREAT KID :laugh::good:**
Click to expand...
Click to collapse
WILL TRY TO BE BRIEF....maybe...
ONLY did the whole QUOTE for the fact this works on newer formats 4.4.x.... (for now)...
IMO, this SHOULD out in the main thread or something.
Seems that just trying to use Chainfire Auto root does not work on 4.4.x...HOWEVER THIS does honestly work right the first time!!! Do need to add that I have tried Auto w/Odin (3.09/3.07/an 1.85) so many times it Nuckin' Futz....
OK, have been in same boat and working extremely hard and long on this issue (rooting SGS3 on 4.4.2) for the past week or so! I do really mean work on this issue. Have read an researched tons ...Starting w/4.3 to 4.4.x, as well as what is coming down the darn pike on this matter. Look up what Mr. Chainfire has posted in the last month... might get folks thinking twice on that new phone purchase, not just the cost, but what they end up with.
Anyway, I want to thank you....
Seems to me, the main thing that has kept me from rooting was this little tid-bit>>> "After it says "PASS" unplug and go right into RECOVERY from this point, (meaning from download mode right to recovery)"....as well as Once in Phliz recovery> RE_ROOT, then boot into system
Truly hope this helps others with there SGS3 (l710)
Thanks Again.
P.S.
reason for the red>So hopefully others on stock 4.4.x, can see 1 honest easy way to root
Jayhawker69 said:
roirraW "edor" ehT....THANKS A MILLION!! I have successfully in ODIN, flashed Philz Touch Recovery onto my S3. I booted into recovery, went in Philz settings, and clicked on the "re-root" option. I rebooted the device into the main system/shell, ran root checker to verify root status.....AND VOILA! ROOT STATUS GRANTED, BISH! I downloaded SuperSU from the play store, and everything seems to be running like butter. Consider this thread CLOSED!
Cheers from Lawrence, Kansas!,
-Brett
Click to expand...
Click to collapse
These steps worked! Thank you both very much!
So usually I don't have any issues with rooting my phone and all. For some unknown reason i just cant seem to root my Sprint Note 4 phone!
Information:
Phone: Sprint Note 4
Model: SM-N910P
Android Version: 6.0.1
Software Version: N910PVPU4DPE1
Build Number: MMB29M.N910PVPU4DPE1
TWRP Version: twrp-3.0.2-0-tbltespr (Which i successfully managed to install)
I used CF-Auto-Root-trltespr-trltespr-smn910p.tar
I did notice that when i flash my auto-root it says "Finding boot image.....Boot image not found, Aborting" under the Boot image patch.
Any ideas on what it means? I'm at a total loss so anything would help me at this point.
imsuckk said:
So usually I don't have any issues with rooting my phone and all. For some unknown reason i just cant seem to root my Sprint Note 4 phone!
Information:
Phone: Sprint Note 4
Model: SM-N910P
Android Version: 6.0.1
Software Version: N910PVPU4DPE1
Build Number: MMB29M.N910PVPU4DPE1
TWRP Version: twrp-3.0.2-0-tbltespr (Which i successfully managed to install)
I used CF-Auto-Root-trltespr-trltespr-smn910p.tar
I did notice that when i flash my auto-root it says "Finding boot image.....Boot image not found, Aborting" under the Boot image patch.
Any ideas on what it means? I'm at a total loss so anything would help me at this point.
Click to expand...
Click to collapse
CF-Auto Root was made to flash with odin, to keep your stock recovery in place. I don't think it works with MM roms.
Just download and flash Supersu from within TWRP. Here's the thread for SuperSu Here.
I always use the Latest version 2.74 here. But you can use the Stable version 2.65 here. They're both in the thread above.
Enjoy!
aaron74 said:
CF-Auto Root was made to flash with odin, to keep your stock recovery in place. I don't think it works with MM roms.
Just download and flash Supersu from within TWRP. Here's the thread for SuperSu Here.
I always use the Latest version 2.74 here. But you can use the Stable version 2.65 here. They're both in the thread above.
Enjoy!
Click to expand...
Click to collapse
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
imsuckk said:
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
Click to expand...
Click to collapse
No you don't have to wait. You can root. Cf-auto was made by the same person as supersu. It was just intended to root your phone with odin in one step. What it does is temporary installs a custom recovery that roots your phone, then puts back a stock recovery (At least something like that). But it isn't up to date to work with Marshmallow. So you just have to do it manually. I thought you said you already have Twrp recovery but I'll show you all steps. I'm assuming you have odin and know how to use it.
1. Download and install Twrp from this thread. Follow links in thread to download and install with Odin here.
2. Once you get TWRP installed. I suggest you boot into it and make a Full Backup of your phone.
3. Download onto your phone SuperSu 2.74 here.
5. Boot into Twrp and install the supersu file you downloaded.
You're now rooted.
aaron74 said:
No you don't have to wait. You can root. Cf-auto was made by the same person as supersu. It was just intended to root your phone with odin in one step. What it does is temporary installs a custom recovery that roots your phone, then puts back a stock recovery (At least something like that). But it isn't up to date to work with Marshmallow. So you just have to do it manually. I thought you said you already have Twrp recovery but I'll show you all steps. I'm assuming you have odin and know how to use it.
1. Download and install Twrp from this thread. Follow links in thread to download and install with Odin here.
2. Once you get TWRP installed. I suggest you boot into it and make a Full Backup of your phone.
3. Download onto your phone SuperSu 2.74 here.
5. Boot into Twrp and install the supersu file you downloaded.
You're now rooted.
Click to expand...
Click to collapse
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
Oh. That explains it. TWRP ISN'T installed. Let me explain.
1 Download Twrp here.
2 Odin Twrp to phone. Make sure to uncheck auto reboot in odin first. After odin completes it'll say something like all operations done. Just make sure odin is done. It don't take long. Then you have to unplug usb from phone and pull out battery for 10 sec. Put battery back in and hold Vol up + Home + Power button until Twrp boots.
3 now twrp is installed and you can install root.
Also backup your phone.
Sorry I'm busy right now and can't post a good post with pics. If that all makes sense then you should be good to go. If you don't understand what I mean I can message you later with some screenshots
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
tar.img is what you should flash in Odin for TWRP. If you are already on TWRP recovery, you can use the .img file to update within TWRP. TWRP makes both these files in flash form; one for Odin flash, the other for TWRP recovery flash. No need to convert. See link below for the Odin flashable TWRP.
Your kernel must already be patched or custom. (Possibly the reason it can't be patched).
When you boot your ROM, check your kernel and bootloader using Galaxy Tools or PhoneInfo for Samsung. If they don't match your last known update, it's possible you've not successfully updated because your reactivation lock is enabled and you didn't notice you failed to update. Nonetheless, check your reactivation lock by going into Settings/Security and uncheck the option.
If failures persist, flash the stock tar in Odin and make sure it flashes.
For the record, latest update for CF AutoRoot for Note 4 does in fact work. But note, you should flash that in Odin over full stock only. Don't try to flash it if you already flashed TWRP. It's intended to back up stock recovery and stock kernel to restore if you full un-root within the SuperSU application. It's been reportedly to be an unknown or dysfunctional but I can confirm it worked for me back on PB5 leaked MM tar. I used the latest update for CF AutoRoot for Note 4 then. Can't imagine anything broke since then but when I realized it was just systemless root, I lost interest. But hey, it has its purpose for those not interested in TWRP recovery and want yo test if OTA is possible with the limited modification. I've yet to test the theory that it may allow OTA update if system ro partition is left untouched. I like sound mods too much to leave system fully stock.
I can recommend an easier way though (if uninterested in systemless root): you don't have to pre-root if flashing a custom ROM. Once you determine your issue or just Odin flash and confirm the stock PE2 tar. Flash the TWRP tar.img file and then factory reset and flash Freeza's Note 4our beta 3.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
https://androidfilehost.com/?fid=24591023225176402
Note: Thank freeza if the clean flash suggested goes as expected. His thread is in the development forum for Sprint Note 4.
Sent from my SM-N910P using Tapatalk
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
aaron74 said:
AmmO0702 said:
looking for the best way to root my sprint note 4. can you help me
Click to expand...
Click to collapse
First off some things you should do before ever flashing or rooting your phone.
1. Make sure ReActivation Lock is OFF. (Its in Settings>Security>Reactivation Lock = make sure its unchecked)
2. Turn on Developer options. (Goto Settings>About device and tap Build Number 4 to 5 times; then develepers options will be in settings menu, goto that and turn on USB Debugging)
3. You'll need Official Samsung Drivers HERE! Install this to your PC!
4. Always Backup Phone!!
Now your set to Flash and Root.
IM gonna assume your on a Stock ROM. To root your gonna need to use Odin to flash TWRP, then once thats done we'll root from there.
You'll need these files :
Odin3.11 from Here. , Thanks to @LMMT, Thank him here. You'll install this to your Windows PC.
TWRP 3.0.2.0 from Here. This file is only for the Sprint Note4 SM-N910P, So that better be the phone you have!! Download and save to PC! You can Thank @bigbiff at this Thread.
Lastly you need SuperSU Here! Thanks to @Chainfire at this Thread! Download and save to your Phones SD card or Internal memory.
Now you have the files. Make sure you dont have samsung Kies running while installing or flashing your phone. Actually Dont have any other programs running when Flashing your phone.
1st - Install Samsung Drivers to your PC.
2nd - Install Odin to your PC.
3rd - Copy SuperSU zip file to your phone.
Now unplug your phone and turn it off. And open Odin Program as Admin. Now on your phone hold down the Vol down button + Home button + Power button at same time until a screen shows a Warning.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then you'll press Volume up to continue to Download Mode.
Once in Download mode plug into usb cord to PC. Your pc should install some drivers then Odin will show your device as connected. Goto options tab in Odin and make sure all the boxes are unchecked except F. Reset Time.
Then click the log tab so we can watch the progress were gonna make. Then click the AP button and load the Twrp file you downloaded into that. If everything looks like my pic then click start. Let it do what it does, dont touch anything until it done. Once down unplug phone and take out battery for 5 seconds.
Put battery back in and press Vol up + Home + Power until phone boots into Twrp Recovery.
Once in Recovery I sugessst to do a Full Backup.
Then you can Hit Install button in Twrp and find the Super SU file you saved on phone and Install and reboot when it says. Your ROOTED!!
Hope this isnt confusing. It really isnt that hard. But Id be able to show you better in person than in writing.
Click to expand...
Click to collapse
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
Hooked my phone up to Smart Watch and noticed I had a software update. Gonna update my phone then check back in here and try it out! Thanks!
Sent from my SM-N910P using Tapatalk
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
I meant to use CF AutoRoot, one should start with stock kernel and recovery.
There has been some inexplicable loss of systemless root. I don't claim to know what is causing that but prefer the system based root in freeza's ROM.
Your help has been good. I was posting as you were. Otherwise, I may not have posted that earlier.
Sent from my SM-N910P using Tapatalk
imsuckk said:
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
Click to expand...
Click to collapse
Really do not understand why Cf-autoroot do not work for you. I rooted my device just yesterday with Odin and Cf-autoroot works just fine
Sent from my SM-N910P using XDA-Developers mobile app
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
Man, I am still not rooted when I boot the phone up. Still am getting the same Boot Patch error and everything.
samep said:
I meant to use CF AutoRoot, one should start with stock kernel and recovery.
There has been some inexplicable loss of systemless root. I don't claim to know what is causing that but prefer the system based root in freeza's ROM.
Your help has been good. I was posting as you were. Otherwise, I may not have posted that earlier.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Oh ok, I must have read too fast. My bad.
I often wondered if anyone had lost root cause Yeah I lost root app a couple times with systemless root. Especially Always after I install idones unlock app I lose it. Have to reflash stock kernel and root.
I downloaded @freeza note four Rom last week. Haven't had time to install and play with it yet. I didn't know it had system root. It looks promising. I know he has done a lot for our device. As has a bunch of devs on this site. I know Ive seen your name all through here too. Thanks for all your help.
I don't claim to be a Dev but I like to hack, mod, and figure stuff out. And I've learned most the stuff I know here on XDA. So when I see someone I can help I try to give back to the community.
---------- Post added at 07:39 PM ---------- Previous post was at 07:19 PM ----------
imsuckk said:
Man, I am still not rooted when I boot the phone up. Still am getting the same Boot Patch error and everything.
Click to expand...
Click to collapse
Ok lets get to the bottom of this. Im gonna walk you through getting a fresh stock boot image and then rooting it.
First do you mean when you start your phone it says that?
Or when you go to flash cf autoroot it shows that?
And Can you boot into TWRP recovery?
aaron74 said:
Oh ok, I must have read too fast. My bad.
I often wondered if anyone had lost root cause Yeah I lost root app a couple times with systemless root. Especially Always after I install idones unlock app I lose it. Have to reflash stock kernel and root.
I downloaded @freeza note four Rom last week. Haven't had time to install and play with it yet. I didn't know it had system root. It looks promising. I know he has done a lot for our device. As has a bunch of devs on this site. I know Ive seen your name all through here too. Thanks for all your help.
I don't claim to be a Dev but I like to hack, mod, and figure stuff out. And I've learned most the stuff I know here on XDA. So when I see someone I can help I try to give back to the community.
---------- Post added at 07:39 PM ---------- Previous post was at 07:19 PM ----------
Ok lets get to the bottom of this. Im gonna walk you through getting a fresh stock boot image and then rooting it.
First do you mean when you start your phone it says that?
Or when you go to flash cf autoroot it shows that?
And Can you boot into TWRP recovery?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
When I flash SuperSU it says that, and yes i am able to get into TWRP still.
imsuckk said:
When I flash SuperSU it says that, and yes i am able to get into TWRP still.
Click to expand...
Click to collapse
ok AWEsome. Where gonna see if a copy of your stock kernal is on your phone.
1. Boot into Recovery, Click Advanced, and then File Manager
you should now see the root of your .file system. Click on the Data folder and scroll down do you see a file that start with stock_boot_?
aaron74 said:
ok AWEsome. Where gonna see if a copy of your stock kernal is on your phone.
1. Boot into Recovery, Click Advanced, and then File Manager
you should now see the root of your .file system. Click on the Data folder and scroll down do you see a file that start with stock_boot_?
Click to expand...
Click to collapse
I do not see that. It could be that I just did a fresh update to PE2 and have a totally fresh ROM (with TWRP installed)
imsuckk said:
I do not see that. It could be that I just did a fresh update to PE2 and have a totally fresh ROM (with TWRP installed)
Click to expand...
Click to collapse
Ok Im gonna PM you so not to fill this thread with bunch of mess
aaron74 said:
Ok Im gonna PM you so not to fill this thread with bunch of mess
Click to expand...
Click to collapse
Alright thanks man!
Sent from my SM-N910P using Tapatalk
imsuckk said:
Alright thanks man!
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Besides the stuff we disgust. If that dont work. You could install a pre rooted rom. Or if you really want to figure out why it wasnt working.
I would start with clean slate and download the PE2 tar. Wipe phone and flash it. Reinstall Twrp and Supersu.
Hope it works! Have to get off here for awhile!!
Let me know if you got it!
Will the same method work on pj1 ?
Team Win Recovery Project 3.0.2-0
This is for the Chinese SM-G9300 and SM-G9308 Qualcomm models only! Do not flash on Exynos models!
If you have a SM-G9350 look here instead!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys7china.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
You will need to unlock your bootloader now. To do this, download the app "CROM Service By Samsung Electronics Co., Ltd." from the Galaxy Apps store and run it.
Follow the instructions in the CROM Service app to allow your device to accept custom images in download mode.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for heroqltechn.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 7.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest no-verity-opt-encrypt zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
It will allow your system to boot after swiping to enable modifications or using backup/restore in TWRP.
It should also allow you to use [Format Data] and prevent encryption, allowing you to use your data partition and internal storage inside TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2.0 - Official release on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (USA): https://github.com/jcadduono/android_device_samsung_heroqlte (android-6.0)
Device tree (China): https://github.com/TeamWin/android_device_samsung_heroqltechn (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_msm8996 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S7 China, Tool/Utility for the Samsung Galaxy S7
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_heroqltechn
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-09-09
Created 2016-09-10
Last Updated 2016-11-22
As a joke, here you go USA!
https://idlekernel.com/twrp/heroqlte/twrp-3.0.2-0-heroqlte.tar.md5
It works for all USA variants of the S7, but you can't boot it because of your signature enforcement (locked bootloader)! Muahahahaha!
jcadduono said:
As a joke, here you go USA!
https://idlekernel.com/twrp/heroqlte/twrp-3.0.2-0-heroqlte.tar.md5
It works for all USA variants of the S7, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
xD I'm waiting for the damn bootloader's to be unlocked!
I have a Samsung Galaxy S7 SM-G930U (unlocked version) ........I currently am using this device in nigeria and i want to unlock bootloader/root/ install TWRP but it doesnt allow the TWRP install on ODIN.... MY device is using the Qualcomm/ not the EXYNOSS
phone model: SM-G930U
device type: heroqlteue
product name: heroqlteue
product code: SM-G930UZKAXAA
CSC: XAA USA/US
BOOTLOADER: G930UUEU2APG9
Hardware: qcom/msm8996
please help.
obone410 said:
I have a Samsung Galaxy S7 SM-G930U (unlocked version) ........I currently am using this device in nigeria and i want to unlock bootloader/root/ install TWRP but it doesnt allow the TWRP install on ODIN.... MY device is using the Qualcomm/ not the EXYNOSS
phone model: SM-G930U
device type: heroqlteue
product name: heroqlteue
product code: SM-G930UZKAXAA
CSC: XAA USA/US
BOOTLOADER: G930UUEU2APG9
Hardware: qcom/msm8996
please help.
Click to expand...
Click to collapse
U = USA (only SIM unlocked, still bootloader locked, it's the same as all the other USA variants)
it will never be able to use TWRP.
jcadduono said:
U = USA (only SIM unlocked, still bootloader locked, it's the same as all the other USA variants)
it will never be able to use TWRP.
Click to expand...
Click to collapse
WHY HAST THOU FORSAKEN ME!!!!
But really tho when you say never... Will I never be able to use GOV Tuner?
Also for anyone stuck in a loop after trying to flash TWRP (don't ask how I know this!) if you restart into download mode and press up you can get it to restart normally from there. FYI.
Any luck with the v variants? G935v / G930v? Could we boot a recovery and not flash it like the guys in the amazon fire forum?
G9300 APE3 root ok, but modem version unknown. modem fatal.
来自我的 Mi-4c 上的 Tapatalk
i have a s7 g9308 from china mobile, pls confirm if this will gonna work and can i install gapps aftet thid method works?
knoxgin said:
i have a s7 g9308 from china mobile, pls confirm if this will gonna work and can i install gapps aftet thid method works?
Click to expand...
Click to collapse
no idea, you should let me know. back up system in twrp and then flash your gapps package, probably "ARM64 -> 6.0 -> Nano" (it is minimal but has everything that can't be installed from play store) from opengapps.org to be safest. Any other google app can be installed from play store if that succeeds.
If it fails to work, simply restore the system backup you made and you're back to how you were!
jcadduono said:
no idea, you should let me know. back up system in twrp and then flash your gapps package, probably "ARM64 -> 6.0 -> Nano" (it is minimal but has everything that can't be installed from play store) from opengapps.org to be safest. Any other google app can be installed from play store if that succeeds.
If it fails to work, simply restore the system backup you made and you're back to how you were!
Click to expand...
Click to collapse
ok tnx sir. but this method really work? if i follow the steps? coz if i brick it , i dnt know How to flash it back to stock tru odin.
installing twrp works, but if i flash supersu only, then reboot, root works but lost my signal and if i flash no-verity-opt-encrypt zip. only then reboot, it works and has signal, and if i flash both, rooted but no signal, pls help.. also, gapps x64 6.0 nano get errors in google play services, cant download or update apps, i think the problem sir is in supersu, coz everytime i flash it i lost my signal, im glad i have my backup in twrp , pls help fix this bug, i want a rooted and working gapps, coz china mobile dnt have gapps pre installed
jcadduono said:
As a joke, here you go USA!
https://idlekernel.com/twrp/heroqlte/twrp-3.0.2-0-heroqlte.tar.md5
It works for all USA variants of the S7, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
Holly sh**!!! I flashed this and I have TWRP in on US variant now.
Can't read!
---------- Post added at 06:20 PM ---------- Previous post was at 06:18 PM ----------
KillerClaw321 said:
xD I'm waiting for the damn bootloader's to be unlocked!
Click to expand...
Click to collapse
There is always hope (Looks at Note 4)
evrycard said:
Holly sh**!!! I flashed this and I have TWRP in on US variant now.
Click to expand...
Click to collapse
So flashed this on which US S7 variant and software , 930U or ?
evrycard said:
Holly sh**!!! I flashed this and I have TWRP in on US variant now.
Click to expand...
Click to collapse
Seriously? Or troll?
jcadduono said:
As a joke, here you go USA!
https://idlekernel.com/twrp/heroqlte/twrp-3.0.2-0-heroqlte.tar.md5
It works for all USA variants of the S7, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
What do you mean it works but we can't flash it? I understand that our bootloader is locked but can we flash this with FlashFire on our G930A?
Thank you
dirtydodge said:
What do you mean it works but we can't flash it? I understand that our bootloader is locked but can we flash this with FlashFire on our G930A?
Thank you
Click to expand...
Click to collapse
Joking with the OP.
dirtydodge said:
What do you mean it works but we can't flash it? I understand that our bootloader is locked but can we flash this with FlashFire on our G930A?
Thank you
Click to expand...
Click to collapse
fixed the post, you can flash it but you can't boot it due to locked bootloader (signature enforcement)
Help me
i tried to flash your recovery and stock rom after that. So my mobile is starting bootloop. Can you help me to solve this problem. I think a stock recovery is a solution to solve that
- WARNING -
This Guide is not failproof, if you do anything wrong with your device while following this guide, i won't be held responsible if you brick or hard damage your device. I insist about that but you must extract all of your data (Photos, Videos, Music, Apps, Accounts, Messages, ETC) Before proceeding or else you will end up with a loss of data, again i'm still not responsible if you lose all of your data without backing up. I WARNED YOU.
Well, you have a Galaxy S6 edge+ lying around and you want to get back to Lolipop? You want to downgrade? Well then you're in the right place!
So......downgrading to lolipop...... some people claimed it can be done by deleting some file in the odin .tar but that never worked for me.
If you have the sw rev check fail error upon downgrading....this is the guide for you!
This will wipe all your data including internal storage (depending on how you do it)
Confirmed working on my Galaxy S6 edge+ SM-G928F [It should work on Note5 but no promises from now on]
Advantages :
Downgrade procedure is safe, simple.
Your phone should boot faster
battery life should last longer [i said it should]
You can get the animated lock screen animations back.
Get old touchwiz back. [i like the 5.1.1 version]
disadvantages:
1. You cannot boot TWRP while on the downgraded bootloader
2. You will only have system-wide root. DO NOT flash systemless or it will not boot (but nobody cares)
3. Fingerprint is not working (still working on that)
4. You can only flash stock nougat from odin. You cannot flash lolipop, marshmallow tar,twrp tar,cf auto root tar or anything else [except if you have a combination firmware]
Ok, let's get started.
Requirements :
A laptop or home PC : At least running Windows 8/8.1 or Windows 10
Your device
Genuine Samsung charging cable [NOT SPONSERED]
Stable internet connection.
Files :
The lastest SAMSUNG Drivers which can be found here : https://developer.samsung.com/android-usb-driver
Odin3 : https://www.samsungodindownload.com/fr/download-for-windows
The firmware you want to downgrade to : I will link my ROM so u can install it.
TWRP [Newest version] : https://twrp.me/samsung/samsunggalaxys6edgeplus.html
Classy Kitchen [for bulding your rom] : https://forum.xda-developers.com/t/...kitchen-for-android-roms-development.3862584/
Now let's get started!
Let's start first by cooking the ROM! Open Classy Kitchen, and then open the ROM you want to use :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Normally the first time you open the program, there shouldn't be any project [except if you used this app before]
Next click "Create new project", "From PC (Browse for one)"
And then chose the path where you saved your firmware. After chosing your firmware, Classy Kitchen will open the firmware automaticly.
After the ROM is now open, click on "ROM utils" and then click on "Deodex ROM" After you Deodex the ROM, we will have to de-bloat it.
On Classy Kitchen, click on "Debloat / Re-Bloat ROM" to Debloat your ROM.
Last step [optional] We will have to De-Knox our ROM. (again optional) But De-Knoxing our ROM can save a lot of space in our phone storage. So i recommend you do.
After De-Knoxing our ROM, we will have to disable DM-Verity Force Encryption in order to Boot into the ROM [Otherwise if you don't your phone will never boot]
Click on "Remove DM-Verity / Force Encryption"
Next that we disabled DM-Verity, We will have to remove the "meta-inf installer"
Click on "Re-Build META-INF installer" and click on remove.
Finally once we have done the modifications on our ROM, we just have to save.
Click on "Build (system.new.dat) ROM (for recovery)"
and then we are done cooking our ROM!
But the guide is not done yet. We will have to install TWRP in the phone.
HOW-TO-PROCEED?
Step-1 Press and hold the power button on your device
Step-2 Chose "Power Off"
Wait for your device to completly Shut-Off.
Step-3 Re-Boot in download mode "odin mode"
Step-4 connect the phone to your computer
Step-5 open Odin3
In Odin, we will have to install TWRP, click on the AP box and chose your TWRP file [the one that you downloaded]
Don't forget to disable "Auto-Reboot" after installation, otherwise your phone will re-boot normal into Android.
At this point, Knox is tripped in your device meaning that your warranty is now expired. Also the Knox features are no longer usable.
On TWRP, click on wipe, "Format Data". A keyboard will pop-up, type "yes"
Type "yes"
Once Data Format is completed, hit home, reboot, recovery.
your phone will reboot into recovery again, hit wipe again, this time we won't format data. Instead we're going to wipe the phone's partitions
Chose in TWRP,
Then swipe to wipe. Then hit home again. Next hit "Install"
Install the ROM you just made with Classy Kitchen. It can be found in "Documents" - "Output" - "Your-ROM"
Transfert it to your phone
Click on the ROM / ZIP file and "swipe to confirm flash"
After the flashing procedure is complete, you will have to wipe the "cache" / Dalvik.
Hit "wipe dalvik/cache"
Then "swipe to wipe"
After you wiped the cache, hit "Reboot System" and hit "Do Not Install"
One last step before you get back to Lolipop. You will need a custom Bootloader in order to boot.
Just download my "custom Bootloader" https://drive.google.com/file/d/1207Guvk8J_L9FSJv2C9BpkeLpWkXtViQ/view?usp=drive_link
After you downloaded my "custom bootloader" you will have to install it.
so get Odin3 and install my bootloader!
After the Bootloader installation is complete, you just have to reboot your device, cross your fingers and hope it boots!
Congratuations! You are back on Lolipop! Enjoy!
1 : If you want to flash a mod in TWRP, you will have to put your phone in download mode, install the stock bootloader in BL tab, install TWRP in AP tab and then click on "start"
2 : If you want to get back into marshmallow / Nougat, you just have to flash stock firmware in Odin3
If you have any issues or any questions, you can DM me but it isn't guaranteed that i will reply.
Here are some screenshots of Lolipop :
Here the device i used.
what about system sound because on 6.1.1 (sorry 6.0.1) sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Nevermind. This comment is deleted
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Actually
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Try download downloading my bootloader again. I made it public
TheWiiGuy said:
Actually
Try download downloading my bootloader again. I made it public
Click to expand...
Click to collapse
Why sound coming like creepy from buzzer only on 6.1.1 interesting..
iskender4444 said:
Why sound coming like creepy from buzzer only on 6.1.1 interesting..
Click to expand...
Click to collapse
Have you downgraded to Lollipop yet?
TheWiiGuy said:
Have you downgraded to Lollipop yet?
Click to expand...
Click to collapse
i had bootloop on samsung galaxy s6 edge plus here the photo:
and can you share the twrp? and is this correct one?
"twrp-3.1.1-0-zenlte.img"
iskender4444 said:
and can you share the twrp? and is this correct one?
"twrp-3.1.1-0-zenlte.img"
Click to expand...
Click to collapse
Yes. This is The Good TWRP. Are you trying to get into recovery? If not then there is a problem with my bootloader
Mind if i upload the New bootloader tomorrow?
iskender4444 said:
i had bootloop on samsung galaxy s6 edge plus here the photo:
Click to expand...
Click to collapse
It looks like the phone is trying to get into stock recovery.
TheWiiGuy said:
It looks like the phone is trying to get into stock recovery.
Click to expand...
Click to collapse
idk and i dont get it why doing this i just re-download twrp official website and still same issue i just flash the twrp but can't enter twrp recovery right know.
iskender4444 said:
idk and i dont get it why doing this i just re-download twrp official website and still same issue i just flash the twrp but can't enter twrp recovery right know.
Click to expand...
Click to collapse
Actually i forgot to mention that you can't boot into TWRP on My custom bootloader. Get back in odin. Re-flash stock bootloader in BL Tab and flash TWRP in the AP Tab. Then try to re-boot onto Custom recovery. Tell me some news.
TheWiiGuy said:
Actually i forgot to mention that you can't boot into TWRP on My custom bootloader. Get back in odin. Re-flash stock bootloader in BL Tab and flash TWRP in the AP Tab. Then try to re-boot onto Custom recovery. Tell me some news.
Click to expand...
Click to collapse
Oh yes. Have you backed up all of your partitions on TWRP?
TheWiiGuy said:
Oh yes. Have you backed up all of your partitions on TWRP?
Click to expand...
Click to collapse
i solved twrp but can't boot same as issue on picture
iskender4444 said:
i solved twrp but can't boot same as issue on picture
Click to expand...
Click to collapse
So you can boot onto TWRP ?
OK. I see the problem.
I Will upload my New bootloader tomorrow.
The current bootloader does not allow to Boot onto TWRP and it can't boot into stock recovery either.
Hopefully the New bootloader should fix your problem. It has stock recovery
TheWiiGuy said:
So you can boot onto TWRP ?
OK. I see the problem.
I Will upload my New bootloader tomorrow.
The current bootloader does not allow to Boot onto TWRP and it can't boot into stock recovery either.
Hopefully the New bootloader should fix your problem. It has stock recovery
Click to expand...
Click to collapse
i have another problem i was trying to flash stock 7.0 rom but gives error same like this.
iskender4444 said:
i have another problem i was trying to flash stock 7.0 rom but gives error same like this.
Click to expand...
Click to collapse
Nevermind this comment is deleted
TheWiiGuy said:
What is your phone model number? I see you are installing firmware for a sm-g780f.
Click to expand...
Click to collapse
no this is for example man mine was g928c