Develop Bugs

[ROOT] Wont Trip Flash Counter (Bell Canada I747M)

Hey Everyone!
This is my first time doing an official ROM repact by injecting Root into the ROM itself so as to not trip the flash counter!
This is for Bell's Canadian S3 SGH-I747M firmware: I747MVLALE8
I know this has recently already been done by MrRobinson for the Canadian carriers but I have done mine slightly differently.
Most of you im sure know of Chainfire and his amazing work, well I love the work he does and it is my opinon that his Root app SuperSU is better then the Superuser one, this may be very minor or non exisist to some people and it all really boils down to Personal perference but as such I perfer SuperSU and love it and want to support his work!
I have tested this myself on my own S3 works great, counter does not increase, and flash time only took me 6 minutes! (some people were complaining about the other root injected roms taking 10 minutes and upwords to 20 to complete)
IMPORTANT NOTE:
This rom has been injected with Chainfires CF root but it is only his SuperSU root app and does not contain any custom CWM recovery or Manager app. Chainfire custom builds his CWM manager app specific to certain devices and is not compatible with the North American varients.
To get the North American LTE version of CWM Recovery please see team epics website at:
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
To install this recovery without tripping the counter you will need to manually copy it over to the memory card block which contains the recovery section of your phone. Once downloaded extract the recovery.img file out of the tar and place it into your sdcard.
Either through ADB shell or using a terminal emulator app on the phone run the following commands:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Remember to do "su" first to grand root access to the ADB shell or terminal emulator otherwise you will not be given the permissions to do the recovery copy on the 2nd command as mentioned above.
1 final note, like all the other root injected roms for the S3, these root methods currently do have not busybox built into them so it is highly recommended for you to download and install the busybox app off the play store [the one by Stephen (Stericson)] to get even more functionality for your rooted device.
~~Link Removed~~
My apologies in advance for uploading to filefactory as they are known to be slow sometimes on downloads. If anyone is able to host it for faster speeds that would be awesome.
EDIT:
For some reason the cache file doesn't properly install and so you are left with a blank CSC. Currently trying to figure out why this is happening as I havn't done anything to the CSC file to begin with. In the mean time I have taken down the link. I recommend getting the one made by MrRobinson for flashing Bells Rom
View the sticky post for his here:
http://forum.xda-developers.com/showthread.php?t=1739426

There is already a thread for this under stickies, but thanks for your contribution anyways.
Sent from my SAMSUNG-SGH-I747 using xda premium

jthrasher47 said:
There is already a thread for this under stickies, but thanks for your contribution anyways.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I am aware of this, I actually made a point of saying so in my post but I guess you skimmed it and didn't see that part?.
I also explain that mine is a bit different and why.

Correct me if I'm wrong, but SuperSu and Superuser and interchangable via. the Play Store. No need to redo the whole rooting process just to change the app.

dbzgod said:
It took me longer because I had to do it without a Linux box, funny enough I manage to do it using my Rooted S2 phone lol.
Click to expand...
Click to collapse
Am I understanding correctly that this method doesn't use odin, and you somehow used another android phone to do it?

danny6514 said:
Correct me if I'm wrong, but SuperSu and Superuser and interchangable via. the Play Store. No need to redo the whole rooting process just to change the app.
Click to expand...
Click to collapse
Yeah they can be changed out, but I released this anyways because I had started work on it right away when the firmware was released and even though MrRobinson had put out root injected roms before me I still wanted to complete what I started and not leave it half done.
I would of had this out at about the same time if not before the others but because of time contraints on my part as well as running into a few problems via doing the whole repack and inject a unique way on my rooted S2 Android phone. Instead of a Linux box I figured out how to do almost all of the repacking steps on an Android phone and then I was delayed trying to figure out 1 important step that required a full Linux box, but discovered an alternate means to do so on Windows.
At any rate I just wanted to post my work (even though late coming) and offer people this alternate root injection Rom.
qwer777 said:
Am I understanding correctly that this method doesn't use odin, and you somehow used another android phone to do it?
Click to expand...
Click to collapse
No you still need to use Odin to flash the firmware. I see your misunderstanding though, I was just trying to explain in my post that since I dont have a Linux box I had to do the repact and inject process over ADB shell via my Rooted Galaxy S II phone for a Linux eviroment.

dbzgod said:
No you still need to use Odin to flash the firmware. I see your misunderstanding though, I was just trying to explain in my post that since I dont have a Linux box I had to do the repact and inject process over ADB shell via my Rooted Galaxy S II phone for a Linux eviroment.
Click to expand...
Click to collapse
Damn! I was really excited! Oh well. I'll need to find me a windows pc.

[Kernel][GT-N8000/13] mybrainhurts 08/25/2012

PLEASE READ THIS POST AND THE FAQ BEFORE POSTING
This post is going to be very brief until I have the time to add more content.
Attached is a kernel with TriangleAway support to permit resetting of your flash counter. However, the kernel has wifi issues on my device - if you have wifi reliability issues you'll probably want to flash a stock kernel in Odin. However, so far, everyone else who has tried this reports their wifi is working fine so it may just be my device.
Kernel source is at https://github.com/Entropy512/kernel_n8013_ics
Initramfs for N8013 is at https://github.com/Entropy512/initramfs_n8013_ics
Initramfs for N8000 is at https://github.com/espenfjo/initramfs_n8000_ics - Thank espenfjo for this one!
It's very barebones for now - Just TA support and removing some excessive debugging printks from drivers that are WAY too chatty.
N8000 support is courtesy of espenfjo

FAQ
Q: How do I install this?
Flash the release in Odin.
Q: I have Linux or MacOS and Heimdall won't work, how do I install?
Samsung changed the partitions around, you need Heimdall built with the patch at https://github.com/teamhacksung/Heimdall/commit/29eb480d6501c6ab650c8af01e60f60c1e38a1ec to flash a kernel. WARNING: If you use this to flash a kernel on an older device you may hardbrick! On older devices, BOOT was the PBL. On newer devices (I9300 and N80xx), it's the kernel!
Q: I want to return to the stock kernel after installing CWM and using this to reset the flash counter, how?
http://forum.xda-developers.com/showthread.php?t=1853209
Q: I used the patched Heimdall above to flash a stock kernel and it triggered by flash counter, WTF?
This scared the crap out of me for a while. For some reason, on this device, Heimdall ALWAYS triggers the flash counter when flashing kernel (and probably recovery) - even if that kernel is a signed Samsung release. Flash using Odin instead, or extract the boot.img from the tar and
Code:
dd if=boot.img of=/dev/block/mmcblk0p5 bs=1024
on a rooted device
Q: Will this work on GT-N8010?
Untested on N8010 (Although one positive user report so far). If you try to use the IR on it, it'll probably crash since that device doesn't have IR.
Q: Will you support the GT-N8000 and GT-N8010?
I hate blind development - but N8010 should be easy. N8000 is harder, however espenfjo (another Cyanogenmod maintainer) did the bringup (defconfig and a first test build) - I have pulled his changes into my source, if you are an N8000 owner thank him for his help. Keep in mind, though, that as a Cyanogenmod maintainer, this kernel will likely stop being maintained once I have a reasonably reliable CM bringup on this device. It's here to serve as an initial reference for other kernel developers on building for this device, and, of course, resetting the flash counter.
Q: Why is wifi so unreliable?
Because Samsung put all sorts of hax in their source that aren't in their shipped kernels. Their shipped kernels seem to be far closer to the I9300 in this regard. The 8/25 release should fix wifi, as it pulls in the I9300 wifi driver.

Change Log
08/25/2012:
Wifi fixed by pulling in I9300 wifi driver
08/23/2012:
Initial release, unreliable wifi on many devices

reserve for misc 2

I'll test on N8010 tonight and provide some feedback.
I've got two backups incase..
Dc
Sent from my GT-N8010 using Tapatalk 2

any chance we will get this support with out flashing a new kernel?

crystalstylez said:
any chance we will get this support with out flashing a new kernel?
Click to expand...
Click to collapse
No, it requires flashing a kernel.
I think Chainfire's approach on some devices is to temp-flash a kernel that supports TA and then revert it, but I'm not sure if he'll support a device he doesn't own with this method.

How to reset counter and get back to stock
Please confirm this is the proper process as I'm exhanging this tablet for a new one.
1. Flash kernel via odin
2. Flash stock Rom via odin
3. Flash stock kernel/recovery via odin
I belive this is right but won't step 3 put the counter back to 1?
Thanks!

ej_424 said:
Please confirm this is the proper process as I'm exhanging this tablet for a new one.
1. Flash kernel via odin
2. Flash stock Rom via odin
3. Flash stock kernel/recovery via odin
I belive this is right but won't step 3 put the counter back to 1?
Thanks!
Click to expand...
Click to collapse
You forgot a step:
1) Flash this with Odin
2) Use the TriangleAway app
3) Flash stock firmware including kernel/recovery in Odin. FYI, http://forum.xda-developers.com/showthread.php?t=1847706 includes EVERYTHING - kernel, recovery, system, etc.
Flashing in Odin only triggers the flash counter if flashing something that wasn't signed by Samsung, if the kernel is from Samsung it won't trigger the counter. Normally this is also the case for Heimdall but it has small issues with this device (see FAQ) that cause it to always trigger the counter, so you need to use Odin.

Entropy512 said:
You forgot a step:
1) Flash this with Odin
2) Use the TriangleAway app
3) Flash stock firmware including kernel/recovery in Odin. FYI, http://forum.xda-developers.com/showthread.php?t=1847706 includes EVERYTHING - kernel, recovery, system, etc.
Flashing in Odin only triggers the flash counter if flashing something that wasn't signed by Samsung, if the kernel is from Samsung it won't trigger the counter. Normally this is also the case for Heimdall but it has small issues with this device (see FAQ) that cause it to always trigger the counter, so you need to use Odin.
Click to expand...
Click to collapse
Ok i did step 1 but I dont see a triangle away app. Is this in recovery? In the Android OS there is no signs of this.
Thanks and sorry if I'm asking a dumb question. Never had a samsung where i needed to do this.

ej_424 said:
Ok i did step 1 but I dont see a triangle away app. Is this in recovery? In the Android OS there is no signs of this.
Thanks and sorry if I'm asking a dumb question. Never had a samsung where i needed to do this.
Click to expand...
Click to collapse
The TriangleAway app would be on the market^H^H^H^H^HGoogle Play Store.

Successful flash on the N8010, no WIFI issues in the past hour.
Triangle Away works too, counter reset to 0.
Great work!!
Dc

espenfjo said:
The TriangleAway app would be on the market^H^H^H^H^HGoogle Play Store.
Click to expand...
Click to collapse
Ha i noticed that afterwards. Question though. I updated so was on yesterdays update that has no root yet as the CWM method doesnt work. Will flashing this kernel still allow the app to work or do i need root too?
If so I guess there shoudl be a stock with root injected odin release soon.

TriangleAway Support for N8000
Hi,
Here is the kernel for N8000.
It is based on the same source as Entropy512, but with support for N8000s radio.
Tested that TA works, 3g/HSDPA and phone calls work.
Sources for the N8000 variant is here:
https://github.com/espenfjo/kernel_n8000_ics
https://github.com/espenfjo/initramfs_n8000_ics

ej_424 said:
Ha i noticed that afterwards. Question though. I updated so was on yesterdays update that has no root yet as the CWM method doesnt work. Will flashing this kernel still allow the app to work or do i need root too?
If so I guess there shoudl be a stock with root injected odin release soon.
Click to expand...
Click to collapse
Maybe your tablet is different than mine, but I was able to root the new update using the CWM method without any issues.
Sent from my GT-N8013 using XDA Premium HD app

jaaka78 said:
Maybe your tablet is different than mine, but I was able to root the new update using the CWM method without any issues.
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
Some people (not all, it's weird) get /system populated with /system/etc/install-recovery.sh - I don't know why some do but others don't.
HOWEVER: The way install-recovery.sh works is to try and convert the kernel image into a recovery image (it's weird) - if the kernel image is altered, the script will bomb. So most likely if you've got this kernel flashed, recovery will no longer get overwritten.
I'll pull espenfjo's defconfig tonight.
BTW, most of my wifi issues occur when streaming video, either via Skifta from a DLNA server or Netflix. They do occur at other times.
If no other N8013 users experience the issues I'm having, I'm going to return the device to stock and exchange it at BB. Normally I would not do such a thing based on behavior with a custom kernel - however if NO ONE else has issues it says my device is really borderline in a unique way.
Espenfjo - any wifi issues?

Entropy512 said:
Espenfjo - any wifi issues?
Click to expand...
Click to collapse
Not this far. It seems to have been stable.
No disconnections, no slow-downs.

espenfjo said:
Not this far. It seems to have been stable.
No disconnections, no slow-downs.
Click to expand...
Click to collapse
So it's either limited to N8013 units, or specific to MY N8013.
I should've released earlier instead of bashing my head against this... I might have discovered this and started working on a CM device tree earlier.
Still can't figure out why the stock kernel works fine though...
Another thing I notice, especially when video streaming, are frequent notifications that I'm connected to a network I'm already connected to - with no apparent transfer interruptions (although Skifta may just cache like a boss.)
Can N8013 users beat on this for a while to see how wifi behaves for them? I originally assumed it would be broken for all but it sounds like it might just be my unit.

So I could use this to reset my counter then Odin your new rooted tar , I still need to figure out how to get spen to work I am hoping your new tar will fix all my issues
Sent from a Baked Black Jelly Belly

davidrules7778 said:
So I could use this to reset my counter then Odin your new rooted tar , I still need to figure out how to get spen to work I am hoping your new tar will fix all my issues
Sent from a Baked Black Jelly Belly
Click to expand...
Click to collapse
If you wipe with STOCK recovery it might - seems like most of those who had weird issues wiped with CWM. It takes measures to protect /data/media that can result in unclean wipes sometimes.

[SGH-T889] CF-Auto-Root

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

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

Download
2013.05.20 --- CF-Auto-Root
SuperSU: v1.30
Download:
SGH-T889: CF-Auto-Root-t0ltetmo-t0ltetmo-sght889.zip
--- History ---
2013.05.20: SuperSU v1.30
2013.02.20: SuperSU v1.05
2012.12.02: SuperSU v0.98
2012.10.28: SuperSU v0.96

Did Samsung/Tmobile release a stock firmware image ?

teshxx said:
Did Samsung/Tmobile release a stock firmware image ?
Click to expand...
Click to collapse
Nope.

Chainfire said:
Nope.
Click to expand...
Click to collapse
Hmm. How did you get the stock recovery then ? I thought you couldn't use the recovery from a rooted device.

teshxx said:
Hmm. How did you get the stock recovery then ? I thought you couldn't use the recovery from a rooted device.
Click to expand...
Click to collapse
Somebody rooted through a modified kernel instead of a modified recovery, and as such was able to dump the stock recovery.

Chainfire said:
Somebody rooted through a modified kernel instead of a modified recovery, and as such was able to dump the stock recovery.
Click to expand...
Click to collapse
Nice! Thanks.
---------- Post added at 04:16 PM ---------- Previous post was at 04:08 PM ----------
Chainfire said:
Somebody rooted through a modified kernel instead of a modified recovery, and as such was able to dump the stock recovery.
Click to expand...
Click to collapse
Since this has the stock recovery, does it mean I can have SU and still be able to receive OTA updates ? (Just picking your brain and learning)
Thanks.

teshxx said:
Since this has the stock recovery, does it mean I can have SU and still be able to receive OTA updates ? (Just picking your brain and learning)
Click to expand...
Click to collapse
Probably is as far as I can go

Mobile Odin & Triangle away should work now ? Thank for your magic..:good:
Edit: Triangle Away work , Mobile Odin not support yet.I just got SuperSU pro & ADBDT insecure and many thank for ADBD information .

Man, that was fast. I was so excited to get that to you but never in a million years would have guessed you would have gotten it done that quick. Thank you, thank you, thank you. Lol. U truly are a legend

chain will i keep the stock kernel?

nightfox11 said:
chain will i keep the stock kernel?
Click to expand...
Click to collapse
From the OP:
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
So yes, you will keep the stock kernel.

The toolkit thread seemed to imply you couldn't root and and then unroot without hiding the flash triangle, but that's what your other tool now does right? I'm still in the TMobile making up my mind process and I don't want a potential barrier to returning the phone (love the phone, still unsure about service).

No matter what I do, my phone continues to say it is 'modified'.
Originally I rooted w/the toolkit, installed a custom rom.
Today I ran CF-Auto-Root to restore the stock recovery, then ran triangle away. After rebooting, my phone still says modified.
Is there anything I can do to change this? Need to return the phone.
Jason

JasonJoel said:
No matter what I do, my phone continues to say it is 'modified'.
Originally I rooted w/the toolkit, installed a custom rom.
Today I ran CF-Auto-Root to restore the stock recovery, then ran triangle away. After rebooting, my phone still says modified.
Is there anything I can do to change this? Need to return the phone.
Click to expand...
Click to collapse
You really need to flash a full stock firmware again ... not sure if that is yet available.

JasonJoel said:
No matter what I do, my phone continues to say it is 'modified'.
Originally I rooted w/the toolkit, installed a custom rom.
Today I ran CF-Auto-Root to restore the stock recovery, then ran triangle away. After rebooting, my phone still says modified.
Is there anything I can do to change this? Need to return the phone.
Jason
Click to expand...
Click to collapse
This thread lists the exact steps you need to revert - if all images are available - http://forum.xda-developers.com/showthread.php?t=1494114

I don't see the model support number

Chainfire said:
You really need to flash a full stock firmware again ... not sure if that is yet available.
Click to expand...
Click to collapse
Yeah, I think you are right. I think I'll just try to restore one of the near-stock ROMs and see if they'll be nice and take it back. If not, I'll just have to eBay it.
Love the phone, returning it because T-Mobile service is really bad where I am. So am going back to AT&T or Verizon.
Jason

chaoz102 said:
I don't see the model support number
Click to expand...
Click to collapse
Really? It's literally next to the download link. It's impossible to miss.

[GUIDE] INSTALLING TWRP on LGG2 (VZW, AT&T, TMobile, KT, d802, others) [UPDATED]

NOTE! This guide is extremely old and likely isnt up to date. I cannot maintain it any more. If anyone is willing to take it over and fix any issues, let me know!
TOOK THE OTA AND GOT STUCK IN RECOVERY LOOP? DERP, DONT TAKE OTAS, DUH. ANYWAYS, IF YOU CANT GET INTO DOWNLOAD MODE AFTER OTA, DO THIS
GUIDE:
Thanks to Bliss who worked the exploit into Loki, Dees_Troy built TWRP for us, djkinetic, Huskehn, and myself tested.
So good news folks! TWRP is now working on LG G2 thanks to an updated loki patch from bliss. Note that Loki patch is not necessarily an unlocked bootloader, but for the end user there is basically no difference. We can flash kernels (when they exist) roms (when they exist) recoveries etc etc. A full bootloader unlock could come someday, but this is all you will need until then.
First off, if you have issues with ADB not connecting, try THESE DRIVERS
The install is super simple, and you have two or 3 options.
Download the img for your device:
AT&T IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
Verizon IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
TMobile IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
Korean Telecom IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
d802 IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
For other models, click HERE and scroll down to find the files beginning with d2, and see if any of the folders sound like your model.
NOTE FOR THESE DOWNLOADS! READ ME! UPDATE! Ok, so if you look in the download page for your device and you are getting a zip file, this is a flashable zip, but it cannot be treated the same as an IMG file in this guide. You need to flash an older one that is a .img file, and then use that to flash the newer zip.
YOU MUST ALREADY BE ROOTED! follow This guide to do so if you arent. BE AWARE THAT THIS ROOTING METHOD ONLY WORKS BEFORE TAKING THE OTA. IF YOU ARE UPDATED AND UNABLE TO ROOT, FOR NOW THE ONLY WAY IS TO FLASH BACK TO STOCK AND ROOT BEFORE THE OTA, THEN TAKE THE OTA, THEN INSTALL TWRP
NOTE THAT ALL GUIDES BELOW ARE REFERENCING THE VZW img file. Be sure to replace it with whatever version you downloaded!
ABSOLUTELY DO NOT FLASH ANYTHING NOT MADE FOR YOU PHONE SPECIFICALLY!
OPTION 1 RECOMMENDED The way I tested it in #lg-g2 Possibly safer as loki runs some safety checks first. Download loki from github here Click download zip on the right. and go into the bin folder of the zip. push loki flash and the img like so:
Code:
adb push loki_flash /data/local/tmp/loki_flash
adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
adb shell
[B][COLOR="DarkOrange"](IF YOU DONT SEE A # prompt, type su to get it.)[/COLOR][/B]
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
exit
adb reboot recovery
-------------------------------------------------------------------------------------
OPTION 2 via dd. Push just the recovery img like this:
Code:
adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
adb shell
[B][COLOR="DarkOrange"](IF YOU DONT SEE A # prompt, type su to get it.)[/COLOR][/B]
cd /data/local/tmp
dd if=/data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
--------------------------------------------
OPTION 3 easy, untested (as of time of writing) install it from goomanager on the phone! This aparantly does work bu you have to manually browse to the file or something... anyone who's tried care to clarify?
I tried and cant figure out where you find the recovery. I recommend Option 1 or 2
----------------------------------------------
Troubleshooting:
If you get "Failed to open aboot for reading." when following method 1, Be sure you have the # prompt, not $. If you rooted properly you should alutomatically have # in shell, but if not just type su to get it. then run the flashing command.
If you had confusion based on the pushing steps because the two img names listed in the command were different, my bad. the filenames changed while I was writing from test version to final, I missed replacing the first name in the commands. Look at the post again as it is fixed now.
If adb reboot doesnt work, make sure that "exit" command fully exited you out of the adb shell prompt. you should be at standard command prompt for that. type exit again if you arent, or heck just open a new command prompt
-------------------------------------------------------------------------
Be happy with what you have, so soon. Be sure to thank all the devs and donate to them![/SIZE][/U]

Got stuck trying to send the recovery to my ATT G2, replacing verizon files, renamed all the files including recovery file to RECOVERY and got it running. TWRP up and running. WOOOHOOO, let the roms begin lol

What? You mean no one cares whether or not I get this device only what @scrosler gets?
I kid, I kid.
Nice work on getting TWRP on the device. Now it is time for something truly awesome to happen, now that this first step has been taken.
Thread Cleaned

can someone confirm sucessful TWRP installation via GooManager? This is the only way i feel comfortable installing it at the moment can someone confirm this method is working?

Walter21026 said:
can someone confirm sucessful TWRP installation via GooManager? This is the only way i feel comfortable installing it at the moment can someone confirm this method is working?
Click to expand...
Click to collapse
I'd like to know this as well, please

This doesn't mean anything about the bootloader does it? You still have to run the stock kernal?

If this works as the loki for the S4 did, then we will have access to flash everything. Kernel, modem, and ROM. There are no boundaries.
Sent from my LG-D800 using Tapatalk 4

JustusIV said:
This doesn't mean anything about the bootloader does it? You still have to run the stock kernal?
Click to expand...
Click to collapse
Currently this is a work around. Bootloader is still locked up tight

Goo says no recovery found for this device.
Sent from my LG-D800 using XDA Premium 4 mobile app

Basically the bootloader no longer matters except for the purity of beating them at their own game. I am sure there are other benefits, but crackflashers will have our fix
Sent from my LG-D800 using Tapatalk 4

i tried thru goomanager i went in to the install open script and it says no recoveries are available

HUGH Thanks to everyone that made this possible! :victory: You guys are the reason I stick with android and never worry about buying the latest devices.
Patience paid off. :highfive:
Now Bring on the ROMS!!!!!:laugh:

Doesn't work for me. I get a "cannot stat 'g2vzw.img': No such file or directory"

Do I need to root before this
Nvm I'm dumb
Sent from my VS980 4G using XDA Premium 4 mobile app

Since there is no file named simply "g2vzw.img" from the OP download links, it's not letting me do the step:
adb push g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.0-g2vzw.img
and tells me that no such file or directory exists, which is true.
Confused....

Han Solo 1 said:
Since there is no file named simply "g2vzw.img" from the OP download links, it's not letting me do the step:
adb push g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.0-g2vzw.img
and tells me that no such file or directory exists, which is true.
Confused....
Click to expand...
Click to collapse
i was about to try, then saw this when reading through it. i don't get it.

So in theory an OTA will patch this just like the S4 so be careful with updates.
Wish i had mine in my hands but i dont have my upgrade till the 29th.

jayochs said:
i was about to try, then saw this when reading through it. i don't get it.
Click to expand...
Click to collapse
Hopefully the OP will chime in here soon.

JustusIV said:
So in theory an OTA will patch this just like the S4 so be careful updates.
Wish i had mine in my hands but i dont have my upgrade till the 29th.
Click to expand...
Click to collapse
Stop by the store or CS they will push it up for you no problem. They did for me just ask nicely
Sent from my LG-D800 using XDA Premium 4 mobile app

Han Solo 1 said:
Hopefully the OP will chime in here soon.
Click to expand...
Click to collapse
i'm also frekaing out because this is the first i heard about this chinese root method possibly having spyware..that's the method i used, and despite the fact i deleted their superuser app immediately, i'm wondering if i should go back to stock and do all that bs just to root again with the new method..

[GUIDE] Root T999 (variants) on android 4.3 AND remove knox

WARNING: Following any of these instructions WILL void your warranty,
and could possibly cause irreparable harm to your device (i.e. bricked)
If you do Not understand these risks, stop here and do Not proceed.
If you do Not know how to use Odin, stop here and do Not proceed.
This guide is ONLY for SGH-T999 variants that are ALREADY RUNNING android 4.3
If you do Not have a SGH-T999 variant, stop here and do Not proceed.
If you are Not currently running android 4.3, stop here and do Not proceed.
I am not responsible for anything that happens to your device. YOU chose to follow this guide.
I have the SGH-T999V (samsung galaxy S3, canada, Videotron)
I flashed the full 4.3 firmware from samsung-updates.com as soon as it became available ... and then I tried to root it the usual ways
However knox prevented the superSu app from running, and it closed immediately, and obviously root was Not available to any app
This method will obtain ROOT and REMOVE the knox garbage
note ... altho it is optional to remove knox, I have Not tested without removing knox and do Not know if root will work using this method (guide) with knox still installed !
I did NOT create this method ... I simply found it, read thru user comments, and used it
FULL CREDIT goes to
@upndwn4par for the method ... the thread is here
@Kaito95 for the Knox Removal script ... the thread is here
@Dees_Troy for the TWRP recovery
@Chainfire for SuperSu
as you can see, this method was for the AT&T, Rogers, Bell, Telus Samsung Galaxy S3 ... I747 variants, I believe
So here is how I achieved a successful root on 4.3 using the above method, with adjustments for our T999 variant
Using Method #2
1. Download required files
a) download Odin 3.07 to your PC​
b) download the latest TWRP recovery for your device, in TAR format, to your PC
click on your device here
scroll down on your device page to the section called Download - Odin Flashable Tar
below that, click on the Select the latest .tar file from here link
scroll to the bottom of the files and click on the latest TAR version
note to d2tmo users ... thanks to @Perseus71 it has been noted that 2.6 versions may have issues on your device, and it is recommended that you choose the 2.5.0.0 TAR version
example: Mine looks like this: openrecovery-twrp-2.6.3.0-d2can.tar
note to T999V users ... both d2can and d2tmo work for our device ... I personally use d2can​
c) download SuperSu 1.65 zip to your DEVICE​
c) download Knox Removal zip to your DEVICE​
2. Reboot into Download mode ... VolumeDOWN + Power + Home
Run Odin
make sure that re-partition is NOT checked!
click the PDA button and point to the TWRP recovery TAR file that you downloaded above
connect your device to the computer ... wait briefly
the COMM port in top left box should turn blue
click Start
when it is done, PASSED, and phone has rebooted, disconnect device
3. Reboot into Recovery mode ... VolumeUP + Power + Home
Flash (install) the Knox Remover zip
Flash (install) the SuperSu zip ... it is version 1.65, current is 1.80, so it will prompt us to update later :good:
Reboot System
4. Update SuperSu from the Play Store
5. Open SuperSu
it should prompt that it needs to update the binary
accept and let it update the binary the Normal way
6. Reboot
7. Enjoy rooted 4.3, knox-free :laugh: :good:
​
thanks again to @Perseus71 for noting that it is possible that the default Enforcing mode of SElinux may cause issues with the ability and/or performance of some root apps despite being granted root permission
if you are experiencing similar issues, he recommends that you check out the SELINUX Status Changer app.
[I have Not personally tested this app]

reserved
in case

You may also wish to mention the SELINUX Status Changer. Here's the Thread.
With it enabled, root won't be stable.
Ahem. First ?
EDIT - TWRP 2.6.x.x has trouble remounting and formatting /Data. You may wish to reccomend version 2.5.0.0

Perseus71 said:
You may also wish to mention the SELINUX Status Changer. Here's the Thread.
With it enabled, root won't be stable.
Ahem. First ?
EDIT - TWRP 2.6.x.x has trouble remounting and formatting /Data. You may wish to reccomend version 2.5.0.0
Click to expand...
Click to collapse
hi and thanks for your input
I just looked at that SELINUX Status Changer thread and will keep an eye on it ... but for now I won't add it cuz:
the dev says it is pre-alpha version
Mine is Enforcing and root seems stable and hasn't had any problems, yet ... 4 days so far
SElinux is here to stay, and there's a big difference between proper (Google) implementation and samching implementation ... root blocked by samching, but not by standard android enforcing #BAM
congrats on being first, lol
what kind of things are you referring to when you say that root won't be stable?
what is your device d2 id?
I haven't had any problems with twrp 2.6.3 for d2can
THAT is something I WILL add, for your specific device
any particular reason you're recommending all the way back to 2.5 instead of just earlier 2.6 version?

cLogic said:
what kind of things are you referring to when you say that root won't be stable?
what is your device d2 id?
I haven't had any problems with twrp 2.6.3 for d2can
THAT is something I WILL add, for your specific device
any particular reason you're recommending all the way back to 2.5 instead of just earlier 2.6 version?
Click to expand...
Click to collapse
I have D2TMO AKA SGH-T999. Yes this is specific to my variant. I tested all the 2.6.x versions to establish that the /Data Problem exists in all these versions.
As to Root, well, Certain apps such as Nandroid Manager, and other apps have difficulty performing Root operation despite SuperSU granting it. @Aerowinder has a lot of stories. May I suggest you please visit the D2TMO Leaked 4.3 Rom thread in development for more details ?

Perseus71 said:
I have D2TMO AKA SGH-T999. Yes this is specific to my variant. I tested all the 2.6.x versions to establish that the /Data Problem exists in all these versions.
As to Root, well, Certain apps such as Nandroid Manager, and other apps have difficulty performing Root operation despite SuperSU granting it. @Aerowinder has a lot of stories. May I suggest you please visit the D2TMO Leaked 4.3 Rom thread in development for more details ?
Click to expand...
Click to collapse
fair enough ... thanks again for your input ... OP updated

Did this to the letter and soft bricked as soon as I flashed the mod zip in twrp. Stuck on pulsing samsung logo.
Had to reflash. Tried twice just to be sure.
(T999) (root, 4.3 stock)

trepoman said:
Did this to the letter and soft bricked as soon as I flashed the mod zip in twrp. Stuck on pulsing samsung logo.
Had to reflash. Tried twice just to be sure.
(T999) (root, 4.3 stock)
Click to expand...
Click to collapse
what do you mean ... bricked as soon as you flashed mod zip? you mean the knox removal script?
not sure how that's even possible
if you see the pulsing logo, then you rebooted
your T999 is rooted?
meaning it was before, or everything was fine after you did it twice?

cLogic said:
what do you mean ... bricked as soon as you flashed mod zip? you mean the knox removal script?
not sure how that's even possible
if you see the pulsing logo, then you rebooted
your T999 is rooted?
meaning it was before, or everything was fine after you did it twice?
Click to expand...
Click to collapse
The native tether mod. Knox remover worked fine.
Phone is rooted, stock 4.3.
Flashed tether mod in twrp recovery, which succeed but phone would not boot past the pulsing Samsung afterwards (10 minutes of pulsing, never booted past that) nor would it boot to recovery. I could get to boot loader luckily. I pulled the battery and tried again, same thing. Flashed stock 4.3 in Odin to get phone alive, tried flashing tether mod again, exact same result and same solution. HTH.
So close to clicking buy now on a nexus 5...

trepoman said:
The native tether mod. Knox remover worked fine.
Phone is rooted, stock 4.3.
Flashed tether mod in twrp recovery, which succeed but phone would not boot past the pulsing Samsung afterwards (10 minutes of pulsing, never booted past that) nor would it boot to recovery. I could get to boot loader luckily. I pulled the battery and tried again, same thing. Flashed stock 4.3 in Odin to get phone alive, tried flashing tether mod again, exact same result and same solution. HTH.
So close to clicking buy now on a nexus 5...
Click to expand...
Click to collapse
ummm .. not sure what this tether mod is that you are talking about, but it's not part of this guide, lol
this guide simply flashes the knox removal script (to delete knox files) and superSu (to root)

cLogic said:
ummm .. not sure what this tether mod is that you are talking about, but it's not part of this guide, lol
this guide simply flashes the knox removal script (to delete knox files) and superSu (to root)
Click to expand...
Click to collapse
Confounded facts. Always kicking my ass.
This is what happens when I stay up too late and try to do too many things. Linked from another thread and had too many tabs open.
Delete.

Thanks for the post. Sadly, no dice for me. I was directed to this post after creating my own. I've really held off asking for help, but only conclusion I can come to is I got one of those phones that just flat out won't root. Tried everything I can think of. Samsung Galaxy s3, SGH-T999v, 4.3, Wind (Canada). The Odin steps worked, when I boot into recovery, just get the stock android recover menu (original issue I've been having). Nothing seems to work in the slightest.

So I followed this to the letter and it all went well. Except, while the device seems to be rooted, SuperSU seems to be granting permissions to apps, Root Check Pro reports the device is rooted... I still can't use any apps that require root access. GameCIH doesn't work. ROM Manager doesn't work. Nothing wants to work.
Why is this happening? Because every step seemed to go flawlessly. Also, I have no idea how to put it back to stock if I wanted to try and start over lol.
[EDIT]
Oh yeah. Pertinent information. Samsung Galaxy S3 T999V through Mobilicity (Canada) running 4.3.
Used the 2.5 tar rather than the 2.6.
Also set SElinux to permissive.

ksec said:
Thanks for the post. Sadly, no dice for me. I was directed to this post after creating my own. I've really held off asking for help, but only conclusion I can come to is I got one of those phones that just flat out won't root. Tried everything I can think of. Samsung Galaxy s3, SGH-T999v, 4.3, Wind (Canada). The Odin steps worked, when I boot into recovery, just get the stock android recover menu (original issue I've been having). Nothing seems to work in the slightest.
Click to expand...
Click to collapse
are you sure you're running stock 4.3 ? baseband MK5 ?
re-do the Odin steps, except uncheck the auto reboot option .. so that it stops after successfully pushing the recovery tar
unplug the phone from the pc .. it should still be in download mode
pull the battery
then put it back in
boot into recovery immediately
if you see the TWRP recovery, great!, complete the guide and you'll be knox free and rooted
if that worked then there are two files that you seem to still have that are putting stock recovery back on normal boot .. post results here and I'll find them for you

Ergonyx said:
So I followed this to the letter and it all went well. Except, while the device seems to be rooted, SuperSU seems to be granting permissions to apps, Root Check Pro reports the device is rooted... I still can't use any apps that require root access. GameCIH doesn't work. ROM Manager doesn't work. Nothing wants to work.
Why is this happening? Because every step seemed to go flawlessly. Also, I have no idea how to put it back to stock if I wanted to try and start over lol.
[EDIT]
Oh yeah. Pertinent information. Samsung Galaxy S3 T999V through Mobilicity (Canada) running 4.3.
Used the 2.5 tar rather than the 2.6.
Also set SElinux to permissive.
Click to expand...
Click to collapse
did you go into superSu and update it's binary?
what do you mean, exactly, by apps won't work ?
do they run? you said they are being granted permission.
how were they installed?
we're they restored using Titanium?
the 2.5 TWRP was recommended for tmobile users.. we are T999V, can use d2can 2.6.3.0 or d2tmo 2.6.3.1

cLogic said:
did you go into superSu and update it's binary?
what do you mean, exactly, by apps won't work ?
do they run? you said they are being granted permission.
how were they installed?
we're they restored using Titanium?
the 2.5 TWRP was recommended for tmobile users.. we are T999V, can use d2can 2.6.3.0 or d2tmo 2.6.3.1
Click to expand...
Click to collapse
I updated the the SuperSU binary.
The apps will open but when it attempts to do anything requiring root access it is denied or fails.
SuperSU and Knox were installed through the TWRP recovery boot thing as the guide specified. Other things were either installed from the app store or downloaded APK files. I didn't have Titanium at the time I attempted rooting my phone. Wasn't mentioned in the guide so I never got it. I have the basic version now from the play store now. As I'm sure you can tell, I've never rooted my device before. Always had a friend do it for me.
Should I just restore to a stock install (not sure how to do this) and then try again? Especially now that I know the 2.5 warning was specifically for T-Mobile users? Or can I just put the 2.6X version on my phone and try again? lol

it's working
@ cLogic
Thanks a lot man, thanks to you I successfully root my sgh-t999v (stock android 4.3)

I've managed to use GooManager from the Google Play store to install latest TWRP and to flash the 4.3 mod.

Having issues when trying this. I followed all the steps and received no errors. But when the SuperSu ap tries to open on my phone it crashes, the ap only phone is stable.
I have Tomo G3 4.3 Stock rom
Flashed the TW 2.5.0.0 version
Rebooted into the touch recovery
Ran Knox removal
Ran SuperSu
Booted
Knox is not in my list off apps
SuperSu does show
Cant not open supersu, updating binarys does not work since the app crashes.
(Edit)--> Redid the whole process but did not let the phone reboot during the TW flash and the Zip installs. Seemed to of fixed the issue. (Edit)
Thanks added

I flashed Stock 4.3 via Odin before coming across this guide and now my device seems to be stuck at the boot screen. My question is, if I haven't completely booted, can I reflash using the modified version of 4.3 (root, deodexed, knox removed)? Do I have any other options right now?