Develop Bugs

[HOWTO] [ROOT] No Tripping Flash Counter - Root Injected L900VPALJC +[TWRP] + more

This is a root injected FACTORY Stock L900VPALJ1 Odin Flashable Image. You flash this in Odin just as you would the completely stock ROM from samsung. I've simply injected the su binary and SuperSu app so you now have rooted stock image.
So if you want to keep your device stock yet have the functionality of root without tripping the counter or messing up OTA updates then this would be your best bet.
You can get ODIN here
and the drivers for the SPH-L900 so ODIN can detect your phone can be found at Samsung's site. Click on the Manuals & Downloads tab at the bottom and then on Software for the latest driver.
Instructions:
First, Download Image:
New Full Rom VPALJC
Mirror 1: root66_SPR_L900VPALJC.7z
Orig Release JB 4.1.1
Mirror 1: root66_SPR_L900VPALJ1.7z
Mirror 2: root66_SPR_L900VPALJ1.7z
Second, Extract and Flash:
Extract the root66_SPR_L900VPALJ1.tar.md5 from the .7z file you downloaded.
Use Odin, put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66_SPR_L900VPALJ1.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE.
OTA Updates:
Stock Recovery: Once rooted with above method, if you receive a notification for an OTA update, it has been verified you can use OTA RootKeeper to retain root through the update process.
Non-Stock Recovery: If you have loaded a non-stock recovery (per below) you can simply use it to flash the OTA update flashable zip I've created.
Mirror 1: OTA Update LJ1 to LJC
Mirror 2: OTA Update LJ1 to LJC
Optional, Recovery (will trip counter):
It seems loading any custom recovery will trip the download mode flash counter. Loading a non stock recovery will also prevent you from successfully applying any OTA updates however here is a procedure for any who want a non-stock recovery:
Currently I see TWRP has support for this device so the instructions here will install that recovery.
Option 1: Download GooManager from the Play store. Once installed click the menu and select "Install OpenRecovery Script".
Option 2: Download the TWRP recovery image here. Copy it to the /sdcard of your phone.
Connect your phone to your computer and use adb
type adb shell
once in the shell run su
then
dd if=/sdcard/openrecovery-twrp-2.3.1.1-t0ltespr.img of=/dev/block/mmcblk0p9
Alternate if unfamiliar with adb commands
Grab android terminal emulator from the play store and run the same commands starting with su and then the dd command.
De-Bloater
If you've made it this far with a stock, rooted phone with CWM or TWRP and you don't want to flash a custom rom (which will do its own de-bloating) you can check out my mrRobinson Note II De-Bloater to easily get rid of bloat system apps you no longer want to see. Simply flash in CWM or TWRP like anything else and you will be presented with a menu system to choose what to remove. If you are unsure it is safe to pick Minimal and still get a decent de-bloat.​
Bonus Files
ODIN Flashable LJC Stock Recovery: SPR_recovery_L900VPALJC.tar.md5
CWM Flashable LJC Modem: modem_CWM_L900VPALJC.zip
History:
I've injected root into other stock images and those threads have a lot of valuable information which could answer some questions that may arise here. If you have time to do some reading here are a few of the informative ones:
Samsung Galaxy S3 [ATT / Bell / Telus / Rogers / Sasktel ]
Samsung Galaxy S3 [TMO / Wind / Mobilicity]
Also did sprint and vzw but there isn't much there that won't be covered above.
FAQ
Does this remove the Sprint bloatware?
A: No. It is same as stock, nothing is removed.
Does this use an unsecured boot.img
A: No. This flashes the stock boot.img in the VPALJ1 image.
If my flash counter has been tripped, and I flash this and reset the counter, will it stay at 0.
A: Yes, as long as you don't then flash a non-stock recovery.
Can I still get OTA updates?
A: Yes if you do not load a custom recovery or remove any system apps OTA updates will still come and be able to be successfully applied. If you want to retain root through the OTA process I'd recommend trying the SuperSU survival mode.

okay will this reset my phone completely? or just install root

Question can this be implemented in to custom roms the "not tripping the counter"
Sent from >> here <<

steviee7 said:
okay will this reset my phone completely? or just install root
Click to expand...
Click to collapse
Just root.

moose1313 said:
Question can this be implemented in to custom roms the "not tripping the counter"
Sent from >> here <<
Click to expand...
Click to collapse
No. Custom roms would trip.

Nice work!

mrRobinson said:
No. Custom roms would trip.
Click to expand...
Click to collapse
Thanks I only asked because I figured if it could be injected as in tricking the phone this is coming from the manufacturer you could also tweak other things and still get away with it. ..Also without an OTA released yet can you say 100% an OTA will go through with no problems if we used this Thanks again
Sent from >> here <<

mrRobinson said:
No. Custom roms would trip.
Click to expand...
Click to collapse
maybe im just a lil special at the moment, i haven't tripped the flash counter yet i learn something when i had the s3 i think that after you flash the tar for the recovery wait till its done (uncheck reboot before u flash) and then pull the battery and it doesnt trip the counter. if im wrong someone please correct me.

Just wanted to let everyone know I did this method then accepted the OTA update and I'm still rooted. Thanks for this!

Very nice! Thank you very much! This will make it easy to go back to stock AND have custom recovery!

wraptor said:
Just wanted to let everyone know I did this method then accepted the OTA update and I'm still rooted. Thanks for this!
Click to expand...
Click to collapse
Anyway u could get this in the hands of devs particularly joshbeach so he can start getting this in the jellybomb rom?
Sent from my SPH-L900 using xda app-developers app

If I odin this, does it reset everything? Seems large for just a reocvery

JBizzleFoSho said:
If I odin this, does it reset everything? Seems large for just a reocvery
Click to expand...
Click to collapse
Its not just a recovery. that's a root method that trips the counter. Maybe you responded in wrong thread.
This will reset nothing, just fyi.

yay gonna run this and flash the new update .... ive been doing dirty jellybomb flashes for quite awhile time a start with a fresh base :good:
---------- Post added at 11:14 AM ---------- Previous post was at 10:28 AM ----------
wraptor said:
Just wanted to let everyone know I did this method then accepted the OTA update and I'm still rooted. Thanks for this!
Click to expand...
Click to collapse
I did it and lost root

fatboypup said:
yay gonna run this and flash the new update .... ive been doing dirty jellybomb flashes for quite awhile time a start with a fresh base :good:
---------- Post added at 11:14 AM ---------- Previous post was at 10:28 AM ----------
I did it and lost root
Click to expand...
Click to collapse
yes you should as it overwrites all /system. use an ota rootkeeper or supersu survival mode to retain root through the ota process.

mrRobinson said:
yes you should as it overwrites all /system. use an ota rootkeeper or supersu survival mode to retain root through the ota process.
Click to expand...
Click to collapse
thanks

Yes sorry must of been delirious last night. Some of my programs that need root (like mybackuppro) still work after the OTA so I just assumed all was good. Titanium backup doesn't however confirming no root =/. Best method to get it back?

wraptor said:
Yes sorry must of been delirious last night. Some of my programs that need root (like mybackuppro) still work after the OTA so I just assumed all was good. Titanium backup doesn't however confirming no root =/. Best method to get it back?
Click to expand...
Click to collapse
i ran CF auto root then installed rootkeeper than flashed the update again ..... still tying to get custom recovery going at the moment TWRP from goo manager says it installed but its not sticking i goto recovery and its still stock

actually i looked at the patch.... I don't see where it would be removing root.... I must be missing something.

fatboypup said:
i ran CF auto root then installed rootkeeper than flashed the update again ..... still tying to get custom recovery going at the moment TWRP from goo manager says it installed but its not sticking i goto recovery and its still stock
Click to expand...
Click to collapse
if you have a root explorer go to /system/etc and delete the install-recovery.sh file you see there. Or just rename it something else like install-recovery.bak

[Q] Unrooted but still has (Device Status: Custom)

So I tried to root my phone (GT-N7100) running on 4.3 Jellybean, but had problems with Knox and Super User so I unrooted the device with Zedomax's help.
1.) Install the custom recovery
2.) Reset the Binary count with Traingle Away
3.) Unrooted with Super User
Root Checker says I dont have root, but Knox and OTA won't let me check for updates. Checked my Device Status still on Custom
I am LOST on what to do.. couldn't find anything. PLS HELP MEEE!! want my phone back to stock like out of the box. Phone is from the Philippines (Globe)
P.S. First time posting here (NOOB!)

FTBLLKiD said:
So I tried to root my phone (GT-N7100) running on 4.3 Jellybean, but had problems with Knox and Super User so I unrooted the device with Zedomax's help.
1.) Install the custom recovery
2.) Reset the Binary count with Traingle Away
3.) Unrooted with Super User
Root Checker says I dont have root, but Knox and OTA won't let me check for updates. Checked my Device Status still on Custom
I am LOST on what to do.. couldn't find anything. PLS HELP MEEE!! want my phone back to stock like out of the box. Phone is from the Philippines (Globe)
P.S. First time posting here (NOOB!)
Click to expand...
Click to collapse
Now, we do not any solution for tripping Knox and resetting knox counter. But you've to flash your phone with official rom by downloading it from: sampro.pl/firmware/android/samsung-gt-n7100/.
First check your phone's current version by dialing *#1234# and then select proper rom from provided website. This might (But not guarantee it) help you to avail official updates.

m.b.jikre said:
Now, we do not any solution for tripping Knox and resetting knox counter. But you've to flash your phone with official rom by downloading it from: sampro.pl/firmware/android/samsung-gt-n7100/.
First check your phone's current version by dialing *#1234# and then select proper rom from provided website. This might (But not guarantee it) help you to avail official updates.
Click to expand...
Click to collapse
Thanks!! Will try it. Will this solve the device status problem?:victory:

m.b.jikre said:
Now, we do not any solution for tripping Knox and resetting knox counter. But you've to flash your phone with official rom by downloading it from: sampro.pl/firmware/android/samsung-gt-n7100/.
First check your phone's current version by dialing *#1234# and then select proper rom from provided website. This might (But not guarantee it) help you to avail official updates.
Click to expand...
Click to collapse
Found my Country and carrier but only CSC matches with my phone not the build number? Should I continue?

FTBLLKiD said:
Thanks!! Will try it. Will this solve the device status problem?:victory:
Click to expand...
Click to collapse
Definitely sure about Knox it would not restore to 0x0. But you'll avail official update.
Sent from my GT-N7100 using XDA Premium 4 mobile app
---------- Post added at 09:14 PM ---------- Previous post was at 09:10 PM ----------
FTBLLKiD said:
Found my Country and carrier but only CSC matches with my phone not the build number? Should I continue?
Click to expand...
Click to collapse
As per my advice try to find replica of your stock firmware. You may, but backup first your efs partition. In case if that no matched for your device it'd probably delete your IMEI, wifi, bluetooth address. Later it helps easily restore the data without any kinda worries.
Sent from my GT-N7100 using XDA Premium 4 mobile app

m.b.jikre said:
Definitely sure about Knox it would not restore to 0x0. But you'll avail official update.
Sent from my GT-N7100 using XDA Premium 4 mobile app
---------- Post added at 09:14 PM ---------- Previous post was at 09:10 PM ----------
As per my advice try to find replica of your stock firmware. You may, but backup first your efs partition. In case if that no matched for your device it'd probably delete your IMEI, wifi, bluetooth address. Later it helps easily restore the data without any kinda worries.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Correct me if i'm wrong, but in order to back-up EFS you need a rooted phone right? or is there a safe way to back-up EFS
with an unrooted phone

FTBLLKiD said:
Correct me if i'm wrong, but in order to back-up EFS you need a rooted phone right? or is there a safe way to back-up EFS
with an unrooted phone
Click to expand...
Click to collapse
You don't need a rooted phone at all, but a custom recovery like - CWM recovery, Philz Touch, TWRP etc.

m.b.jikre said:
You don't need a rooted phone at all, but a custom recovery like - CWM recovery, Philz Touch, TWRP etc.
Click to expand...
Click to collapse
Thanks!! now I can remove my other thread about rooting with TRWP recovery. LOL!

m.b.jikre said:
You don't need a rooted phone at all, but a custom recovery like - CWM recovery, Philz Touch, TWRP etc.
Click to expand...
Click to collapse
hey got another question, why do I need to flash the stock rom/firmware when I just rooted my phone and installed Super User but didn't flash a custom rom, only used Odin to get Philz touch 5.15 and used Philz touch for SuperSU. sorry for asking too much

FTBLLKiD said:
hey got another question, why do I need to flash the stock rom/firmware when I just rooted my phone and installed Super User but didn't flash a custom rom, only used Odin to get Philz touch 5.15 and used Philz touch for SuperSU. sorry for asking too much
Click to expand...
Click to collapse
Nope you didn't need at all, that's needed when you're selling your phone, because person next to you whomever will likely to need stocked phone... And all.
Sent from my GT-N7100 using XDA Premium 4 mobile app

FTBLLKiD said:
hey got another question, why do I need to flash the stock rom/firmware when I just rooted my phone and installed Super User but didn't flash a custom rom, only used Odin to get Philz touch 5.15 and used Philz touch for SuperSU. sorry for asking too much
Click to expand...
Click to collapse
when you rooted your phone, there's a modified inside the system, that's why samsung bootloader will detect it as "modified/custom" instead of "official". I know your ROM is still official after you unroot it. But, unroot just remove the access to the root/system file. Whatever modified during the rooting process earlier will remain the same. Therefore, if you want to get an "official" status back, you have to flash stock original firmware after you have clean binary, & unroot your device.
cheers.

antique_sonic said:
when you rooted your phone, there's a modified inside the system, that's why samsung bootloader will detect it as "modified/custom" instead of "official". I know your ROM is still official after you unroot it. But, unroot just remove the access to the root/system file. Whatever modified during the rooting process earlier will remain the same. Therefore, if you want to get an "official" status back, you have to flash stock original firmware after you have clean binary, & unroot your device.
cheers.
Click to expand...
Click to collapse
Hahaha thought Triangle Away would fix that device status problem being Modified/Custom
So you know anyway to download the stock rom quicker. My downloads are always unsuccesful...

FTBLLKiD said:
Hahaha thought Triangle Away would fix that device status problem being Modified/Custom
So you know anyway to download the stock rom quicker. My downloads are always unsuccesful...
Click to expand...
Click to collapse
samfirmware
other than that, I have no idea. Just try to google for the firmware you want. u might get other links from google.

have the same problem with my note 2, and i want to know if the solution provided worked

.

Need help recovering from failed root

I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?

Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk

dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
Click to expand...
Click to collapse
Thanks! I'll give that a shot. But a question before I do something really dumb. Where does this recovery tar file go in odin? PDA?

Yep always PDA
Sent from my SM-P900 using Tapatalk

Worked! I now have rooted KOT49H.T900UEUAND4.

Good stuff
Sent from my SM-P900 using Tapatalk

OK. Here comes the "but". It turns out that I cannot connect over SSL. Wifi works, I have an IP, I can brows non-secure websites. But I cannlt connect to anything https, nor will apps like Google Play connect.
Do we think this is related, or should i start a new thread?
UPDATE: I wiped data and now all is fine. The really interesting thing that I've noticed is that the Device Status is showing as "Official".

JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?

gbr357 said:
JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?
Click to expand...
Click to collapse
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.

Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?

gbr357 said:
Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?
Click to expand...
Click to collapse
I think I would have done that if I had known there was a B5 recovery image available. The guidance that I was given was to flash the B3 image from the P900. And that *did* work fine. Before there was a root flash for the T900, people were using the P900 root with success. Don't know that there is much difference. In the end, either way, you will end up with a B5 recovery image, as that is what Chainfire included in the T900 root file.

Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.

gbr357 said:
Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.
Click to expand...
Click to collapse
Which file from Chainfire did you flash? Was it CF-Auto-Root-v2wifi-v2wifixx-smt900.zip? For me, flashing that after OTAing to ND4 left me unable to boot. Maybe that got fixed in the past couple of day?

Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??

gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Well. technically I wasn't rooted either. I completely removed root with SuperSU.Is your recovery NB5?

JJMT said:
I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?
Click to expand...
Click to collapse
That's the problem I've been writing about for a week. The new OTA update (t900ueuand4) doesn't work with auto-root and crashes exactly where yours did.
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Can you give me the link for the new chainfire file that must have been re-written in the last 2 days
---------- Post added at 11:32 PM ---------- Previous post was at 11:28 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Just re-downloaded the chainfire file and it's identical to the file I got 10 days ago dated May 10th. If you had success flashing it with the firmware t900ueuand4 installed at the time of rooting, then I'll give it a shot too.

JJMT said:
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.
Click to expand...
Click to collapse
All I had to do, was stop after 3. Didn't require a factory reset. Everything is great

The same here. Used the Note 12 recovery mod to unbrick the tablet.
Flashed the CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5 and it works. :good:
Now oor Samsung tablet pro 12.2 is rooted.

dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I ran into a similar issue except my device came up to an error regarding firmware upgrade failed, use kies to recover. I could not get this to work with kies 3. Searching the threads, I found your post. Worked beautifully. The failed attempt did trip Knox. Not sure I care.
Thanks!

Root to sg3 4.4.2 i747m

THERE is a way to root the kit kat 4.4.2 official of the D2CAN ?

brayhanrd said:
THERE is a way to root the kit kat 4.4.2 official of the D2CAN ?
Click to expand...
Click to collapse
Try Towelroot.

vbetts said:
Try Towelroot.
Click to expand...
Click to collapse
that work for you!!! confirmation plz!!

chewingum16 said:
that work for you!!! confirmation plz!!
Click to expand...
Click to collapse
Works like a charm. install towel root let it do it's method then phone will reboot once it reboots install super su from play store and hola!
---------- Post added at 11:40 PM ---------- Previous post was at 11:39 PM ----------
Xami said:
Works like a charm. install towel root let it do it's method then phone will reboot once it reboots install super su from play store and hola!
Click to expand...
Click to collapse
https://mega.co.nz/#!Ah9BmApB!N0W7vyZ23_yhDooMxo-zhF3WYqEioStM8J-opaVjXWk
Flash in odin for recovery

vbetts said:
Try Towelroot.
Click to expand...
Click to collapse
thanks it work like a charm..

Xami said:
Works like a charm. install towel root let it do it's method then phone will reboot once it reboots install super su from play store and hola!
---------- Post added at 11:40 PM ---------- Previous post was at 11:39 PM ----------
https://mega.co.nz/#!Ah9BmApB!N0W7vyZ23_yhDooMxo-zhF3WYqEioStM8J-opaVjXWk
Flash in odin for recovery
Click to expand...
Click to collapse
thanks for help !!! it's the amazing apk in the history of rooooooooot

This rooting method was made by GeoHot. The same guy who unlocked the first iphone back in 2007. He jail broke the ps3 in 2011 then Sony tried to sue him. Then anonymous shut their a$$es down for a good two weeks.

Does towelroot trip the knox counter?

I saw someone say it does not. It preserves the stock recovery so it makes sense that it wouldn't. But if you plan on using a custom recovery or kernel it won't matter as that would trip it anyway.

audit13 said:
Does towelroot trip the knox counter?
Click to expand...
Click to collapse
I used it to root my phone and no my Knox flag is still at 0 so your good to root and have warranty
Sent from my ATT Samsung Galaxy SIII using TapaTalk

Towelroot AT&T Galaxy S3 i747 with 4.4.2 Working.
Towelroot installed with No problems on my AT&T SGH-i747 Galaxy S3 with the new 4.4.2 update. See screenshots below.
Does not affect Knox Warranty Bit! I am staying with factory recovery mode.

so i've tripped my knox, and towelroot says it's incompatible. any suggestions?

Towelroot will only work for NE6 firmware on the I747M. The exploit it uses was patched in NF1/NF2.
you can try cf autoroot, or just flash recovery then flash SuperSU.

I have tried to root my phone, I747M, Canadian, 4.4.2 version, with SRSRoot, it says that process is complete and that everything is OK but root checker says that phone isn't rooted and Superuser icon can't be found anywhere. I tried Towelroot few minutes ago, it says that my phone isn't currently supported. Dunno what to do any more...

No idea what srsroot is... Just flash a supersu update package from my sig. Flash in recovery.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

Recovery won't stay flashed after reboot. Twrp 2.6.3.0 and 2.8 if I don't let phone finish booting into ROM after flashing I can access twrp but there's no storage. Won't mount any partitions, data/system/cache or external/internal SD. If I do let it finish reboot into ROM, then shut down and boot into recovery it reverts back to stock recovery. Towel root and cf auto root both are unsuccessful as well as Kingo. Any help please?
Also tried cwm recovery. Same deal as twrp

Flash recovery again. Use its built in file manager to delete or rename these files and recovery will stay after rebooting.
/system/recovery-from-boot.p
/system/etc/indtall-recovery.sh
Try to mount partitions again. If it fails, go to advanced and copy log to sd. Then attach it here. Do the same if flashing the rom fails.
You may want to try cwm or philz recoveries too.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Ok, thanks. I'm heading home from work n I'll try what u suggested, altho I don't think I'll be able to modify and files, since nothing mounts but I will try. Also definitely won't be copy the log to SD if it won't mount, but could still probably pull it thru adb. Have tried twrp and cwm neither will mount. Will update this post after I try. Thanks

Good point! Sorry bout that! Have you tried philz recovery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

I747 NF1 and NF2 root?
Wrong title. I meant I747M not I747. Anyways, is it possible to just downgrade the NF1 or NF2 kernel to the NE6 kernel then root via towel root then put back the NF1 or NF2 kernel after its rooted?

Systemless Root: SuperSU v2.64... No (custom) Kernel needed

**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.

Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.

balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.

balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
Fixed!

koop1955 said:
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.
Click to expand...
Click to collapse
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).

JoeFCaputo113 said:
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).
Click to expand...
Click to collapse
I wasn't sure if CM13 is already working on International phones.
I only know what I read....
From Chainfire's post:
Rooting procedure:
- flash/upgrade to Marshmellow
- flash modified boot.img
- flash/boot TWRP and sideload latest...
Joe, be careful if you try this. Looks like you need to Odin back to stock.

Does this still void knox?

1619415 said:
Does this still void knox?
Click to expand...
Click to collapse
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.

koop1955 said:
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.
Click to expand...
Click to collapse
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox

1619415 said:
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox
Click to expand...
Click to collapse
Well Merry Christmas!

JoeFCaputo113 said:
Well Merry Christmas!
Click to expand...
Click to collapse
You to
---------- Post added at 01:52 PM ---------- Previous post was at 01:01 PM ----------
Has anyone tried rooting with this method and trying samsumg pay?

Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.

todivefor said:
Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.
Click to expand...
Click to collapse
Try Number 15

1619415 said:
Try Number 15
Click to expand...
Click to collapse
Thanks. Been there done that.
Sent from my SM-T710 using Tapatalk

For those asking about whether this root method trips knox or not. Yes this will trip knox. Anytime you use odin to flash non official Samsung firmware/software then it forever trips knox. Therefore flashing any custom recovery will absolutely trip knox... forever.
Samsung and Android pay apps will not work on rooted devices. Period. The pay apps are intended for official factory software for obvious reasons. Security is the main focus with these types of apps that deal with your personal banking/credit card information. Hence a rooted device is not considered "secure".

using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.

yaibakt said:
using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.
Click to expand...
Click to collapse
Try installing/updating busybox and try removing titanium backups root access them regrant it

JoeFCaputo113 said:
**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.
Click to expand...
Click to collapse
Nice work will give this a go soon.

1619415 said:
Try installing/updating busybox and try removing titanium backups root access them regrant it
Click to expand...
Click to collapse
thank you. ill give it a try. :good:

This may be a weird question, but we don't have a stock kernel to flash. Would there be a way to make a zip of a stock kernel and then use this to get root? I'd like to have a custom ROM but with the stability of a stock Kernel. This is the first phone I can think of that I've owned that didn't have a stock kernel with root.