Database Info

[4.4 ROOT] SlapMyMoto 1.0 (Works with MotoWPNoMo)

My apologies for taking so long, life is hectic. This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4.
First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.
SlapMyMoto requires you to be on the 4.2.2 Camera update, you can find the firmware for your device below:
ATT- http://sbf.droid-developers.org/download.php?device=0&file=22
Verizon - http://sbf.droid-developers.org/download.php?device=0&file=55
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/showthread.php?t=2509590 or http://rootzwiki.com/topic/107098-root-rockmymoto-yes-even-the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Then either wait, or toggle your bluetooth. Once the device reboots, you will have root.

{
"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"
}
After taking the 4.4 OTA in step 3, if you then take on the 4.4.2 OTA update afterwards, the write protection off will be reverted and /system/ will once again be locked. There is no known way at this time to reverse this for users with locked bootloaders.
If you are on 4.2.x, you will be prompted for the 4.4 OTA update before getting the 4.4.2 OTA. You should complete step 4 before deciding to take on the 4.4.2 OTA or not.
Other relivent quotes from jcase:
jcase said:
XxSinisteRxX said:
The only thing i didn't understand was the "restore to 4.2.2 camera update" part, and [...] i'm already on 4.2.2.
Click to expand...
Click to collapse
[...]you skipped a step...
Rooted devices rarely handle OTAs very well, especially if they do not have a recovery anymore. Restore to [stock], and continue.
Click to expand...
Click to collapse
^(From another thread, but a comon question in this one)^
jcase said:
_litz said:
Quoting from Step 3: "Once the device has rebooted, please take the 4.4 OTA."
So what happens if the only OTA available is 4.4.2?
Click to expand...
Click to collapse
The device is not rooted at the step when you are taking the 4.4 OTA. The 4.4 update.zip is available from other sources and can be sideloaded in recovery.
Click to expand...
Click to collapse
_litz said:
FYI, for Verizon, I believe I've found the 4.4 update zip here :
http://downloadandroidfiles.org/download-blur_version-139-15-1-ghost_verizon-verizon-en-us-zip/
Click to expand...
Click to collapse
Possible mirror, not verified: magnet:?xt=urn:btih:CDARPSOTRY7CO4EY6K6SNWVASPBPX46S
jcase said:
_litz said:
Ok ... so what if you use the 0.5c method, where you replace the recovery with the customized boot image, that enabled write protection?
Click to expand...
Click to collapse
You can't boot a customized image.
_litz said:
Will that method work for 4.4.2 when it comes along?
Click to expand...
Click to collapse
No it won't work in 4.4.2, nor will it work with the 4.4 bootloaders.
Click to expand...
Click to collapse
jcase said:
lulajardim said:
I know you stated before that you have no intention on developing new root methods for the Moto X.
But is there any chance you have reconsidered and decided to take a look on 4.4.2?
Click to expand...
Click to collapse
No time, sorry.
No one mentions custom bootloader.
I am aware 0.5c works, but it has it's own flaws hence no longer beign available. Don't take OTAs with root, it is not a smart move.
JC
Click to expand...
Click to collapse
jcase said:
aviwdoowks said:
[What is] the benefit gained by this procedure.
Click to expand...
Click to collapse
Starting with the MotoX, Motorola started applying low level write protection to parts of the flash memory (in this case just /system). Root alone does not give us the ability to modify anything in system. My original hackjob that we used to bypass this has been fixed in Android 4.4. This is required if you want to actually install su into the /system partition.
Click to expand...
Click to collapse
jcase said:
tacitus54 said:
What happened to the flashing recovery.img, before taking the update to 4.4 and then flashing the 4.2.2 bootloader.
Click to expand...
Click to collapse
Previously we were using my workaround to write to system, now we are using MotoWPNoMo to gain write to system, as it is a better solution. No more recovery hackery needed.
Click to expand...
Click to collapse
Note: I will be reviewing threads and duplicating posts here to ease others finding them. PM me if you feel you have been misquoted or have something I missed.

You are the MAN!!! Amazing work!

Says he won't release a root method for 4.4, has to deal with whiny, entitled people that think he's selfish for doing so, and still ends up releasing something. Now that's what I call a class act.

i just went from 6 to midnight. damn, i love this community. now just need xposed for 4.4 and all will be right in the world.

10$ sent to you sir.
Thank you!

freak4dell said:
Says he won't release a root method for 4.4, has to deal with whiny, entitled people that think he's selfish for doing so, and still ends up releasing something. Now that's what I call a class act.
Click to expand...
Click to collapse
Actually, i didn't really release a new exploit, and I won't be. This is the same primary exploits as motoroot/rockmymoto/pwnmymoto, just instead of installing su, it plants a "backdoor". Since they allowed us to downgrade, we were able to do this.

jcase said:
Actually, i didn't really release a new exploit, and I won't be. This is the same primary exploits as motoroot/rockmymoto/pwnmymoto, just instead of installing su, it plants a "backdoor". Since they allowed us to downgrade, we were able to do this.
Click to expand...
Click to collapse
True, but a method is a method, in my eyes.
I gotta wonder if Motorola left the ability to downgrade as somewhat of a subtle way of making up to the community for not being able to unlock the AT&T and Verizon versions. They're just too good at making secure bootloaders to make me think that it was just overlooked.

Thank You!!!

Thank you for all the great and hard work you do for everyone in the consumer motox community.
I will not whine or nag, I will wait patiently until it is complete and ready. I don't have as much time for testing and tinkering like in the droidx days.
So again, jcase, thank you thank you!
Sent from my XT1060 using Tapatalk

wifi tethering
This is awesome news, however, does anyone know if wifi tethering works on 4.4? I've heard that it's broken on kk.

Thanks jcase! Rooting vzw on 4.4 worked great!

If I did these steps correctly, should I see the following message when opening SuperSU:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"

Do you mean gpt.bin and logo.bin? Those are only ones in the camera OTA. I really should have checked before pushing the setup.sh, cause now I just boot to fastboot and don't wanna flash the wrong thing.

Sinderan said:
Do you mean gpt.bin and logo.bin? Those are only ones in the camera OTA. I really should have checked before pushing the setup.sh, cause now I just boot to fastboot and don't wanna flash the wrong thing.
Click to expand...
Click to collapse
From the 4.2.2 camera firmware, I clarified in OP now.

jcase said:
From the 4.2.2 camera firmware, I clarified in OP now.
Click to expand...
Click to collapse
Ok, I thought so, but the .mismatched extensions made me a little nervous to flash.

Awesome! Can't test it yet though, as I am in Canada on Rogers and we haven't gotten the update yet. It's still a relief knowing that I can get root when I get the update though. Thanks!

goose71 said:
This is awesome news, however, does anyone know if wifi tethering works on 4.4? I've heard that it's broken on kk.
Click to expand...
Click to collapse
can anyone confirm this?

@jcase, i know we're waiting for an update/fix for the reboot recovery issue, but i thought i'd mention that step 5 didn't work as described for me:
Step 5)
adb push recovery.sh /data/local/tmp/setup.sh
adb reboot
(It will reboot, then quickly reboot straight to the bootloader)
Click to expand...
Click to collapse
the last part didn't happen. after pushing the recovery.sh file (to data local as setup.sh), then doing an adb reboot, the phone never automatically reboots to the bootloader. maybe i'm missing something though. are we supposed to "quickly reboot" or is this supposed to happen on its own?

mercado79 said:
@jcase, i know we're waiting for an update/fix for the reboot recovery issue, but i thought i'd mention that step 5 didn't work as described for me:
the last part didn't happen. after pushing the recovery.sh file (to data local as setup.sh), then doing an adb reboot, the phone never automatically reboots to the bootloader. maybe i'm missing something though. are we supposed to "quickly reboot" or is this supposed to happen on its own?
Click to expand...
Click to collapse
It is supposed to do it automatically, but the Verizon model is missing some dependency for this method.
Jcase said he has a fix and will work on it soon, but for now, do not do this on the Verizon model. Return to 4.2.2 for now.

(Q) Has anyone successfully rooted their Note Edge (N915T)?

as the title says, I'm looking to see if anybody knows or has been successful in figuring out how to Root the Note Edge.
I was thinking of using CF 910method but wanted to see what others have done before I started experimenting

zz1049 said:
as the title says, I'm looking to see if anybody knows or has been successful in figuring out how to Root the Note Edge.
I was thinking of using CF 910method but wanted to see what others have done before I started experimenting
Click to expand...
Click to collapse
I dont think many have tried yet. Only a few have gotten there device today, the others are waiting for it in the mail, And i believe all of us arent up to bricking rare device lol.
but yea ill wait on the root until there is a way to no trip knox. I like having the option of returning it. (some places check now)

Yeah I thought about it in being a guinea pig. I'm not trying to spend time recovering this thing.
Until then, I look forward to any positive word to root, not necessarily trying to maintain Knox, but that would be amazing.

I plan on trying today and will post an update. I have the tmobile version and will use the note 4 root method.

I read somewhere the tmobile note 4 root method from chainfire works on the tmobile note edge. I'll be trying that method when I get mine on monday from fedex.
---------- Post added at 09:59 AM ---------- Previous post was at 09:55 AM ----------
lreeb1 said:
I plan on trying today and will post an update. I have the tmobile version and will use the note 4 root method.
Click to expand...
Click to collapse
I read somewhere the tmobile note 4 root method from chainfire works on the tmobile edge. I don't see why the note 4 root method wouldnt work, its the same phone just different screen

I just successfully rooted using the t-mobile chainfire. I followed the directions exactly from the T-Mobile Galaxy Note 4 xda page. It's under general and stickied at the top. In Odin it said failed after flashing the chainfire tar but it appears to have worked just fine. I also flashed the twrp linked in the root how-to, then flashed super su in twrp.
I confirmed root by running SuperSu and also running Titanium Backup.
This is the link I followed:
http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733

lreeb1 said:
I just successfully rooted using the t-mobile chainfire. I followed the directions exactly from the T-Mobile Galaxy Note 4 xda page. It's under general and stickied at the top. In Odin it said failed after flashing the chainfire tar but it appears to have worked just fine. I also flashed the twrp linked in the root how-to, then flashed super su in twrp.
I confirmed root by running SuperSu and also running Titanium Backup.
This is the link I followed:
http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
Click to expand...
Click to collapse
Hey, which TWRP file did you grab? Same from the link?(openrecovery-twrp-2.8.1.1-trltetmo.img)
What's your build #(N915TUVU1ANJL) ?
I'm thinking about doin this as well.

Yes. I used the one from the link.

lreeb1 said:
Yes. I used the one from the link.
Click to expand...
Click to collapse
You grabbed all the files? No problem even though is a different build #?

leprophotography said:
You grabbed all the files? No problem even though is a different build #?
Click to expand...
Click to collapse
I haven't had any issues. I was concerned when Odin showed failed after flashing the chainfire tar but I went ahead and pulled the battery after giving it a moment, booted back into download mode and flashed the twrp recover. I got all the files from the post I linked above, except for Super Su. Follow at your own risk but things went pretty smoothe for me.

lreeb1 said:
I haven't had any issues. I was concerned when Odin showed failed after flashing the chainfire tar but I went ahead and pulled the battery after giving it a moment, booted back into download mode and flashed the twrp recover. I got all the files from the post I linked above, except for Super Su. Follow at your own risk but things went pretty smoothe for me.
Click to expand...
Click to collapse
Thanks for taking the risk!
I did the same minus installing TWRP Recovery after, as I just want my phone to be stock touchwiz (except for root). But using the N910T root method (CF) Did not produce a successful root, do you think it may have been TWRP that actually made the root work?

DO NOT TRY THIS ROOT!!! THIS DOES NOT WORK!!! This will give you Cache and other problems. I have tried this on 3 T-Mobile Galaxy Edge phones and all of them give the same problem. I had to restore the original firmware on all 3 phones. I also had a friend try this and the same results.
OP, lets see some proof!!!

I think I'll wait for the L update before i root. ***Unless a knowledgeable recognized contributor posts a way*** @Chainfire

anyone else been successful or unsuccessful using this method?, kinda stuck in limbo right now!

I think best bet is to just wait for a 100% method especially on a phone so expensive
Sent from my SM-N915T using XDA Free mobile app

I don't really understand what you mean by Cache and other problems. Could you be more specific? I'm not trying to lead anyone afoul, just simply stating I was successful at using the tmobile note root method without any issues.
{
"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"
}

I get the unable to mount cache in TWRP. The Note 4 root messes with the file system and does something with the TWRP. Can you be more specific on how you install SU in TWRP? When you reboot from TWRP and it asks you to install SU, is that when you install it?

Has anyone unlocked the tmobile note edge yet for at&t use

tpinfo4 said:
I get the unable to mount cache in TWRP. The Note 4 root messes with the file system and does something with the TWRP. Can you be more specific on how you install SU in TWRP? When you reboot from TWRP and it asks you to install SU, is that when you install it?
Click to expand...
Click to collapse
I flashed the super su zip in TWRP.
http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
Like I said, I have been using my phone fine since Saturday without issue but I haven't tried to mount the cache so I can't speak to that.

I think there was a misunderstanding on installing SU. I just tried this: Installed TWRP via download mode. Went into recovery and installed the SU file from the link you provided. I rebooted the phone and updated the SU program in the play store. I also installed Titanium. When I clicked on the SU program, it asked to update binary and I clicked "Normal". It came back with a response of "Installation Failed". When I run Titanium, it says "Asking for root rights...." and a popup came from SU that says it has been granted access. It is stuck on the "Asking for roots rights". I also installed Root Checker and it says I do not have root.
Did you update SU from the play store?
lreeb1 said:
I flashed the super su zip in TWRP.
Like I said, I have been using my phone fine since Saturday without issue but I haven't tried to mount the cache so I can't speak to that.
Click to expand...
Click to collapse
---------- Post added at 08:14 PM ---------- Previous post was at 07:53 PM ----------
I also tried the new download from chainfire that has our phone on his list now and same results. I don't believe "lreeb1" has root. When I don't update my SU, it shows I have root to various programs, but the programs all say I don''t have root.
Let me see a screenshot of "Rootchecker"???

help porting twrp to lg g stylo?

i wondered if any dev may be interested in helping port twrp to the new lg g stylo aka g4 stylus? id be happy to donate to the cause. the device can be rooted. http://forum.xda-developers.com/general/general/lg-g-stylo-boost-mobile-t3113080/page2

fix-this! said:
i wondered if any dev may be interested in helping port twrp to the new lg g stylo aka g4 stylus? id be happy to donate to the cause. the device can be rooted. http://forum.xda-developers.com/general/general/lg-g-stylo-boost-mobile-t3113080/page2
Click to expand...
Click to collapse
this would be great...i just got the same phone but on metro pcs...we are trying to get a custom recovery for our g stylo too...although it does seem the metro/tmobile variant of this phone is slightly different spec wise...would that be an issue requiring 2 different ports of twrp?
edit i just found this post http://forum.xda-developers.com/showpost.php?p=60913483&postcount=23 and he claims this will install twrp and root the phone...so i was wondering if that file he says to download is ok to use with the metropcs lg g stylo?

Following in structions on that link did root my metropcs lg stylo. The twrp however, did not work...
Sent from my LGMS631 using XDA Free mobile app

OldAzzNoob said:
Following in structions on that link did root my metropcs lg stylo. The twrp however, did not work...
Sent from my LGMS631 using XDA Free mobile app
Click to expand...
Click to collapse
This is an old thread thanks to Unjustified Dev and fix_this! We have TWRP working. Here is the Thread for that
http://forum.xda-developers.com/android/development/lg-g-stylo-t-mobile-lg-h631tn-t3123165
Same for both T-mobile and Metro PCS

we just need to either unlock the boost bootloader or bump a TWRP recovery the right way to make it work on the locked bootloader

6th_Hokage said:
we just need to either unlock the boost bootloader or bump a TWRP recovery the right way to make it work on the locked bootloader
Click to expand...
Click to collapse
Just noticed this on Bump website - http://apps.codefi.re/bump/
Is there anyone here that was actually close or tried to make a bump of TWRP for boost?

Kolma said:
Just noticed this on Bump website - http://apps.codefi.re/bump/
Is there anyone here that was actually close or tried to make a bump of TWRP for boost?
Click to expand...
Click to collapse
SuperR from android forums was helping me and he used the same bump method that he used on the warp sync, but it didn't work sadly

A couple weeks ago i said i rooted my metro lg stylo and the twrp didnt work. Well i decided to do a full unroot until there was more support. Now i came back to the forums, see theres a working twrp and decide to root my phone again, only now it wont root. The one-click root completes and says im rooted but when i use root checker it says NOT rooted. I open supersu and it says no binary installed.
I think maybe my stock recovery got jacked up when i originally rooted. What do you think? Ive completed the one click root at least 8 times. Phone still wont re-root
Sent from my LGMS631 using XDA Free mobile app

OldAzzNoob said:
A couple weeks ago i said i rooted my metro lg stylo and the twrp didnt work. Well i decided to do a full unroot until there was more support. Now i came back to the forums, see theres a working twrp and decide to root my phone again, only now it wont root. The one-click root completes and says im rooted but when i use root checker it says NOT rooted. I open supersu and it says no binary installed.
I think maybe my stock recovery got jacked up when i originally rooted. What do you think? Ive completed the one click root at least 8 times. Phone still wont re-root
Sent from my LGMS631 using XDA Free mobile app
Click to expand...
Click to collapse
have you tried using the Metro KDZ file for your phone to go back to complete stock?

No i haven't. If you give me a little direction I will do that. I have to admit, I'm more familiar with fixing/unbricking/flashing back to stock on Samsung phones, with Odin and all. I'm still getting used to LG phones. I'd like to be VERY careful flashing anything on this Stylo. I'm becoming very attached, and $200 for a phone is a bit more than I'm used to spending. I'd hate to brick it.
Sent from my LGMS631 using XDA Free mobile app

OldAzzNoob said:
No i haven't. If you give me a little direction I will do that. I have to admit, I'm more familiar with fixing/unbricking/flashing back to stock on Samsung phones, with Odin and all. I'm still getting used to LG phones. I'd like to be VERY careful flashing anything on this Stylo. I'm becoming very attached, and $200 for a phone is a bit more than I'm used to spending. I'd hate to brick it.
Sent from my LGMS631 using XDA Free mobile app
Click to expand...
Click to collapse
If you use the KDZ you wont be able to Root and Bootloader will be LOCK ... So just a warning if you decide to do it

Well thats no bueno. I want my phone rooted. I just cant understand why after the one-click root everything seems like it went fine... I even see the SuperSU app in my apps, but when i click it, it says "no SU binary installed"
Stumped
Sent from my LGMS631 using XDA Free mobile app

OldAzzNoob said:
Well thats no bueno. I want my phone rooted. I just cant understand why after the one-click root everything seems like it went fine... I even see the SuperSU app in my apps, but when i click it, it says "no SU binary installed"
Stumped
Sent from my LGMS631 using XDA Free mobile app
Click to expand...
Click to collapse
If you are still om LP 5.0.2 Try using SEND_COMMAND on Download mode to flash TWRP. Im not 100% sure of this process need to be rooted but i dont think so, when TWRP is flash you can flash SU and give it a shot... Im using my phone to post ill send full detail on how to do ot in a bit

I would sincerely appreciate that! As i said before, I'm still unfamiliar with how to flash on LG phones, right down to "how do you boot into download mode?" so detailed instructions would be appreciated.
And really... I appreciate it
(update)
Ok i figured out how to get to download mode, not too difficult. So i figured while i was hooked up to the computer I'd do some tinkering. I'm not android sdk literate so i didnt get far. I do, however, know enough to use some ADB commands and used ADB REBOOT RECOVERY just to see if my gut was right. I cant reboot recovery. I just get a toppled over android and message saying "no command".
Sent from my LGMS631 using XDA Free mobile app

OldAzzNoob said:
I would sincerely appreciate that! As i said before, I'm still unfamiliar with how to flash on LG phones, right down to "how do you boot into download mode?" so detailed instructions would be appreciated.
And really... I appreciate it
(update)
Ok i figured out how to get to download mode, not too difficult. So i figured while i was hooked up to the computer I'd do some tinkering. I'm not android sdk literate so i didnt get far. I do, however, know enough to use some ADB commands and used ADB REBOOT RECOVERY just to see if my gut was right. I cant reboot recovery. I just get a toppled over android and message saying "no command".
Sent from my LGMS631 using XDA Free mobile app
Click to expand...
Click to collapse
adb doesn't seem to work with download mode cause if it did i wouldn't have a bricked phone right now lol but i am interested in how to send recovery to the device while in download mode cause i have the stock recovery and if i can boot into it then i can adb the correct file that i messed up my phone with

6th_Hokage said:
adb doesn't seem to work with download mode cause if it did i wouldn't have a bricked phone right now lol but i am interested in how to send recovery to the device while in download mode cause i have the stock recovery and if i can boot into it then i can adb the correct file that i messed up my phone with
Click to expand...
Click to collapse
I was going to send him a PM but ill be posting the steps here ....
By the way you are boost right?
Ok for starters download this file LG Root File from this Thread
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
Download and install drovers if you haven't done that yet, ill be posting step in a bit just download the files and have them ready.

I am on a metropcs.
I just need good steps on how to properly flash twrp using the send_command in download mode, as you suggested. And i believe my stock recovery is no longer working...
Its for this reason i believe i cant re-root my phone right now. The binary is installed through recovery, correct?
Sent from my LGMS631 using XDA Free mobile app

OldAzzNoob said:
I am on a metropcs.
I just need good steps on how to properly flash twrp using the send_command in download mode, as you suggested. And i believe my stock recovery is no longer working...
Its for this reason i believe i cant re-root my phone right now. The binary is installed through recovery, correct?
Sent from my LGMS631 using XDA Free mobile app
Click to expand...
Click to collapse
From my understanding that is correct

just waiting on those send instructions.....

OldAzzNoob said:
.
Click to expand...
Click to collapse
6th_Hokage said:
.
Click to expand...
Click to collapse
EDIT : Ok this Process to Flash Recovery (TWRP) is just for METRO PCS and T-MOBILE if you are on LP 5.0.2 , DON'T and i REPEAT DON'T try this if you are on Boost and if you have MetroPCS and T-Mobile OTA 5.1.1
ok here is what you can do and i mean @OldAzzNoob to flash TWRP via Download mode (Thank to @Unjustified Dev for this steps that help me out before)
Steps :
1- Go HERE if you haven't and download from Prerequisites step 1 and 2 (LG Root and LG Drivers @Thank you @Unjustified Dev)
"NOTE: skip Drivers if you have them install already"
{
"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"
}
2- CLICK HERE and download TWRP 2.8.7.0 @Thank you @Unjustified Dev) once downloaded Decompress on your root directory of the SDCard and rename ir " recovery.img " without "
3- Decompress LG Root on Root C: drive for easy access.
4- Enable USB Debugging via Developer Option.(now ready for a test drive )
5- Open Command Prompt and go to where you Decompress the LG Root zip file (in my case is C:\LG_Root )
and Type
Code:
adb devices
after doing so it will show if your device is attach or not (see image)
NOTE : Don't close this command prompt window
6- Nice! Device been detected and ready for some more fun
7- lets go to Download Mode ( click here if you don't know how to )
8- ok now having the Command Prompt window open lets type and press enter
Code:
ports.bat
it will show the ports our phone is using but we are going to use just 1 and is REG_SZ
9- Now that we know what port we are going to be using lets flash this little fella and i mean TWRP image
---------------------------------------------------------------------------------------------------------------------------------------
FLASHING RECOVERY VIA DOWNLOAD MODE
---------------------------------------------------------------------------------------------------------------------------------------
1- Now is time to run Send_Command (NOTE : make sure your COM port number is the one YOUR phone is using this varies per device mine is COM9 yours maybe different or not)
1st.
Code:
Send_Command \\.\COM9
after typing that line it will show just # which mean you are doing great, now lets continue.
Code:
dd if=/storage/external_SD/recovery.img of=/dev/block/bootdevice/by-name/recovery
wait till # show back again after that is finish TWRP should be in place and you are ready to use it
you can just Type LEAVE or pull battery and try manually boot to Custom Recovery.
NOTE : if everything when well i recommend going back to LG_Root using Command Prompt and type ADB DEVICES to check if device is connected after checking that out type ADB REBOOT RECOVERY to boot into recovery just to make sure it flashed correctly.

New Samsung user, where do I start?

Hello everyone, from my new Galaxy S6 Edge on Sprint. I've been with Sprint for 15 years and have been on Android since the HTC Hero. Every time a HTC fagship device on Sprint came out, it found its way into my pocket. I finally decided to jump ship from HTC and give Samsung a shot.
With the Samsung S6 Edge being my first Sammy device, there seems to be a lot I need to learn. Are there any tips or tricks that I should know?
I'm on a cross country drive and picked up the phone in Yakima WA last night. It will be several days before I have access to a PC, so when my trip ends in Wisconsin. I want to have everything researched on how to root and install TWRP.
First of all is this KNOX thing something I should be concerned for? What is the go-to method for root? Best Buy ran the BOI1 update on me yesterday. Is there a one click root available? Anything special needed to know for installing TWRP?
Thanks, misfit0313

misfit0313 said:
Hello everyone, from my new Galaxy S6 Edge on Sprint. I've been with Sprint for 15 years and have been on Android since the HTC Hero. Every time a HTC fagship device on Sprint came out, it found its way into my pocket. I finally decided to jump ship from HTC and give Samsung a shot.
With the Samsung S6 Edge being my first Sammy device, there seems to be a lot I need to learn. Are there any tips or tricks that I should know?
I'm on a cross country drive and picked up the phone in Yakima WA last night. It will be several days before I have access to a PC, so when my trip ends in Wisconsin. I want to have everything researched on how to root and install TWRP.
First of all is this KNOX thing something I should be concerned for? What is the go-to method for root? Best Buy ran the BOI1 update on me yesterday. Is there a one click root available? Anything special needed to know for installing TWRP?
Thanks, misfit0313
Click to expand...
Click to collapse
First you're on the wrong thread. You should be in the Q&A section. First you may need to install the Samsung drivers to your computer. Download the preferred Odin 3.10.6 flashing tool. Go to your phone settings/build number, and tap 10 times until you see developer options enabled. Next go to settings/developer options, scroll down to Oem unlocking and turn it on. Next, to root you will need to use the odin tool to install the custom rooted kernel. Once that's complete, you can install TWRP. I'll include my link to twrp and kernel. Remember to Odin kernel first, then twrp. I don't think I forgot anything.
Follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=3102034
Edit:
Knox will be tripped rooting your phone. Will not be able to use Samsung pay, voids your Samsung warranty so you cant send back to Samsung, but does not void your carrier warranty, you can take it to them. Nothing else to worry about knox, doesn't affect anything.

Soooperstar said:
First you're on the wrong thread. You should be in the Q&A section. First you may need to install the Samsung drivers to your computer. Download the preferred Odin 3.10.6 flashing tool. Go to your phone settings/build number, and tap 10 times until you see developer options enabled. Next go to settings/developer options, scroll down to Oem unlocking and turn it on. Next, to root you will need to use the odin tool to install the custom rooted kernel. Once that's complete, you can install TWRP. I'll include my link to twrp and kernel. Remember to Odin kernel first, then twrp. I don't think I forgot anything.
Follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=3102034
Edit:
Knox will be tripped rooting your phone. Will not be able to use Samsung pay, voids your Samsung warranty so you cant send back to Samsung, but does not void your carrier warranty, you can take it to them. Nothing else to worry about knox, doesn't affect anything.
Click to expand...
Click to collapse
Hey, I have a question... If he's on OI1 can he root and flash TWRP or should he Odin to OH1 then root and flash TWRP and then rom???

JediMindTrixx said:
Hey, I have a question... If he's on OI1 can he root and flash TWRP or should he Odin to OH1 then root and flash TWRP and then rom???
Click to expand...
Click to collapse
No! He should do the normal root process. According to the OI1 update you can't go back. The rom works on OI1 according to reports
{
"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"
}
Sent from my SM-G925P using Tapatalk

Soooperstar said:
No! He should do the normal root process. According to the OI1 update you can't go back. The rom works on OI1 according to reports View attachment 3492662
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
That's right forgot about not being able to go back. Thanks! :good:

Thanks Soooperstar... There's a reason why you shouldn't app and drive at the same time, you accidentally post in the wrong thread.
I've rooted, installed recovery, and S-off'ed every single HTC that I owned, the talk about Odin and KNOX threw me off a bit.

misfit0313 said:
Thanks Soooperstar... There's a reason why you shouldn't app and drive at the same time, you accidentally post in the wrong thread.
I've rooted, installed recovery, and S-off'ed every single HTC that I owned, the talk about Odin and KNOX threw me off a bit.
Click to expand...
Click to collapse
Yea I had the OG EVO back in the day. I know all about it. Samsung is much simpler when it comes to rooting

misfit0313 said:
Thanks Soooperstar... There's a reason why you shouldn't app and drive at the same time, you accidentally post in the wrong thread.
I've rooted, installed recovery, and S-off'ed every single HTC that I owned, the talk about Odin and KNOX threw me off a bit.
Click to expand...
Click to collapse
Odin is like RUU and Knox is Sammy's security...
Sent from my SM-G925P using XDA Free mobile app

This looks like the correct kernel to flash to obtain root? http://forum.xda-developers.com/showthread.php?t=3166293
[KERNEL][925P/R4] UniKernel v8-0001

misfit0313 said:
This looks like the correct kernel to flash to obtain root? http://forum.xda-developers.com/showthread.php?t=3166293
[KERNEL][925P/R4] UniKernel v8-0001
Click to expand...
Click to collapse
Correct.... Be sure to get the 925p

Thank you again. I'm rooted and have TWRP installed. A message popped up afterwards ”unauthorized actions have been detected galaxy s6". It was taken care of by freezing "SecurityLogAgent" with TiBu.

SM-G930T Root Doesn't Void Warranty

The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
This root works on all Marshmallow versions on Android on the T-Mobile S7
{
"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"
}

method
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?

dantehalo said:
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?
Click to expand...
Click to collapse
Yes I am planning to make a video tutorial.
Also I used the method provided here (this is Max Lee's website)
And for now here is great video tutorial (also created by Max Lee) The Video

So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.

revulv said:
So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.
Click to expand...
Click to collapse
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.

Month later
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
KillerClaw321 said:
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.
Click to expand...
Click to collapse

djdubyah said:
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
Click to expand...
Click to collapse
It is the only root method so far. It is not required but you can unencrypt before rooting. Rooting while already encrypted won't cause any harm since /data is encrypted not /system . But I still recommend unencrypting so you don't run into any issues.

Does this work for the latest November 1st update APK1?

Hello, I too would like to know if this is still the current root method and if there have been any changes?

GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.

i cant root my sm9307
KillerClaw321 said:
The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
Click to expand...
Click to collapse
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me

seattlestexan said:
GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.
Click to expand...
Click to collapse
Did the attempt trip your Knox counter?

GeorgeNYer said:
Did the attempt trip your Knox counter?
Click to expand...
Click to collapse
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.

seattlestexan said:
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.
Click to expand...
Click to collapse
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
---------- Post added at 09:55 PM ---------- Previous post was at 09:52 PM ----------
GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
I would try it myself but I'd hate to start over from scratch, I just wanna know if you tried all that is in the video, if not then I would try
Sent from my SM-G930T using Tapatalk

GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
What I listed is what I was able to do. I'm not certain it ever had root access. When it showed "custom" at boot, I couldn't grant anything root access. When it acted more laggy, like was described, the lag was so bad, it wasn't usable. Mind you, these instructions were written prior to the APK1 firmware that was on my G930T from new.

jveewee said:
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me
Click to expand...
Click to collapse
It's smg930t, just search smg930t root max lee

I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.

troby86 said:
I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.
Click to expand...
Click to collapse
And Knox counter wasn't tripped??

GeorgeNYer said:
And Knox counter wasn't tripped??
Click to expand...
Click to collapse
Nope.