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"???
Related
I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.
yea i got it
Seanbest said:
I just got a prompt for a new OTA update, but being rooted and running a ROM I couldn't install it. It gave no new information about the update such as size or fixes. Anyone else get this? I'm on an OC3 based ROM by the way.
Click to expand...
Click to collapse
It is the stage fright update
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Will we be able to flash it some other way?
ClearD said:
Will we be able to flash it some other way?
Click to expand...
Click to collapse
I'm sure there will be soon
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.
I confirm, it is a fix for Stagefright. Baseband version went from I337UCUFNJ4 to I337UCUFNJ5
+ SuperSU is working properly.
Below: Before & After the update
{
"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"
}
New Update Came ..
https://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB419415&cv=820
ClearD said:
Well, on second thought, I just went ahead and let the update run. It completed. Everything appears normal.
Click to expand...
Click to collapse
Were you rooted with the Flashfire method?
Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.
billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
nukesnooper said:
Anytime AT&T or Samsung offer a "security" update FOTA, I cringe. I'm on rooted Lollipop and absolutely have to remain rooted to use Total Recall call recorder (you can't imagine how many times it's saved my ass with baseless promises from AT&T and other utility vendors), so I'm always hesitant to upgrade to any FOTA's that may make it more difficult to either flash a better ROM, or other utilities that it might block. Call me paranoid, but I'm going to hold off and try to find a better solution to threats to my OS. Belarc Security Advisor (Free) is highly respected, and a non-conventional system scan that identifies real threats. Running it yesterday and just now; show no threats. I realize that Stagefright is a threat, but I'm running antivirus software that I trust and keep my phone backed up locally on a regular basis.
Click to expand...
Click to collapse
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.
billbillw said:
Well, I also let it run. Figured worst case, it would be rejected due to root. It ran, no errors, still on root (using Flashfire method). Stagefright detector now shows my device is safe.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
If you're using the Stock AT&T Lolipop, and Flashfire method for rooting, you will be OK to let the update run. It ran with no issues for me and it kept root.
Click to expand...
Click to collapse
That's exactly how I did it. My only concern is that it may install patches that could further restrict future modifications.
I also just completed running Lookout and it found no threats or vulnerabilities. I'm staying where I am until I hear more feedback.
Thanks for your advice. I'll be keeping an eye on it.
It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)
sim_pl said:
It's coming in as a 280mb download, I'm going to see what happens with root (previously used Flashfire)
Click to expand...
Click to collapse
Please Upload .cfg File For Update My Device .. That OTA File /cache .. Check It And Upload It Please And Check fota Folder
UPDATED POST:
I upgraded with the install stock but "keep root" method, using flashfire...
The update failed at 29%.
I did a factory reset, and it still failed at 29%...
What are my options now?
Update:
I used Flashfire to install the tethering addon... I wonder if that is the culprit.
Installing without thethering... will update with results.
And It's a pain to download that ATT update each time. --- Their servers are SLOW!
Same story here. Update stops and phone reboots about a third of the way through. Defrosted all Samsung/AT&T bloat and tried again. Same story. Bummer.
I rooted my wife's 0C3 with Kingroot and tried to take the update. It failed.
Maybe I should try again since I just used triangle away to get rid of the "custom" nag at boot.
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network
billbillw said:
Were you rooted with the Flashfire method?
Click to expand...
Click to collapse
Yes. Rooted with flashfire, on oc3 bootloader. I ran the update through the normal OTA method, not trying to install it through flashfire. It worked fine and root stayed normal. Verified when titanium backup ran last night on its normal schedule.
Well, it updated fine, using just the straight rooted rom, no additional flashes. No more fails at 29%...
It appears that adding in anything extra, de-bloat, hotspot enable, etc. will cause the update to fail.
/sk
Reinstalled the rooted stock ROM and the update worked fine. Still have root. All is groovy.
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.
Hey guys.. I've used these forums for years but never posted so here goes.. I just got the new ZTE GRAND X 3 from cricket.. It seems to be a very decent phone, but I'm a root user for life and I'm guessing since its so new the development isn't even thought about yet.. Yes I've tried every single one click exe./apk. there is.. Including framaroot, towelroot,ect. Trust me I've tried with persistence and nothing.. Constant failures.. I gotta get this device rooted.. Please guys lets do this.. Its running 5.1.1..
Lazeyboy420 said:
Hey guys.. I've used these forums for years but never posted so here goes.. I just got the new ZTE GRAND X 3 from cricket.. It seems to be a very decent phone, but I'm a root user for life and I'm guessing since its so new the development isn't even thought about yet.. Yes I've tried every single one click exe./apk. there is.. Including framaroot, towelroot,ect. Trust me I've tried with persistence and nothing.. Constant failures.. I gotta get this device rooted.. Please guys lets do this.. Its running 5.1.1..
Click to expand...
Click to collapse
I just got one today myself! I'll pull a build proper outta mine and I'll talk with a few ppl I know from here and let's see that happens! Heck, puppy is all shiney and I'll sacrifice it. It's just a thing right?
Any progress on this device?
I feel ya, I've had it since February and I'm going nuts not being able to use Titanium backup or any root apps. What makes this phone so different from others that get root.
Sent from my Z959 using Tapatalk
Bootloader
Well what sucks is I can't seem to boot it to the bootloader. On the other hand the ADB program works it's just when I type adb reboot bootloader it just restarts the phone.
Bounty $25
kingo
so i tried kingo on the computer and it shows root successful. i can run apps that ask for root and appear to work.
but some apps hang when aquiring root, but dont pop up with the normal "no root".
Do you think i should try flashing supersu.zip with flashify and see if it gets permanent "correct" root?
got a expendable z959
i have a phone i dont mind if it happens to brick. so shoot me some ideas on rooting this thing and ill try it
I've tried all I know. Nothing works for me.
im trying now in several ways but im using developer options with OEM Unlock enabled to see if that does anything.
btw i tried the Chinese method and it also said i was rooted but opening flashify said i didnt. See u suppose to give flashify root access. If the Chinese way truly rooted the phone im guessing the Root prompt would appear when u open flashify where you can accept or deny flashify root access, and it doesnt. so im trying other things
Rapture81g said:
im trying now in several ways but im using developer options with OEM Unlock enabled to see if that does anything.
btw i tried the Chinese method and it also said i was rooted but opening flashify said i didnt. See u suppose to give flashify root access. If the Chinese way truly rooted the phone im guessing the Root prompt would appear when u open flashify where you can accept or deny flashify root access, and it doesnt. so im trying other things
Click to expand...
Click to collapse
Also when rooting with kingo if you go into terminal and type SU it just hangs
UPDATE: i have made a mess and did something to lose root so ill be doing that today.
i have had a successful root using kingo root for pc and android. u have to download SuperUser and move a copy to /system/bin and /system/xbin. Took some playing around but was able to get ROM Manager and BusyBox to fully open without errors about su. I cant recall the exact steps i did but i do know it involved Root Browser, ES File Explorer and Explorer because i had to change permissions for SuperUser in order to move them to the ending destination. Cant remember which one accomplished it. But after getting BusyBox and Rom Manager to startup with no problems i click Fix Permissions in Rom Manager and after it fixed permissions it said to reboot and i lost root at that point. So i am going to tinker with it more and hopefully can get a proper way to do it. U also need Developer Options On with Stay Awake, Enable OEM Unlock and USB Debugging ON and root will always fail if you do not disable you windows firewall.
Rapture81g said:
im trying now in several ways but im using developer options with OEM Unlock enabled to see if that does anything.
btw i tried the Chinese method and it also said i was rooted but opening flashify said i didnt. See u suppose to give flashify root access. If the Chinese way truly rooted the phone im guessing the Root prompt would appear when u open flashify where you can accept or deny flashify root access, and it doesnt. so im trying other things
Click to expand...
Click to collapse
Do you know what does OEM unlock mean and does?
Thanks:fingers-crossed:
We now have full root!!
The latest version of Kingo for the PC will give you temp root. The link below will give you full root.
ZTE Write Protection problems solved (Simple)
http://androidforums.com/threads/zte-write-protection-for-zmax-and-other-zte-phones.1040331/
Works perfectly on the Grand X3
---------- Post added at 11:56 PM ---------- Previous post was at 11:34 PM ----------
{
"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 Z959 using XDA-Developers mobile app
cbc0201 said:
We now have full root!!
The latest version of Kingo for the PC will give you temp root. The link below will give you full root.
ZTE Write Protection problems solved (Simple)
http://androidforums.com/threads/zte-write-protection-for-zmax-and-other-zte-phones.1040331/
Works perfectly on the Grand X3
---------- Post added at 11:56 PM ---------- Previous post was at 11:34 PM ----------
Sent from my Z959 using XDA-Developers mobile app
Click to expand...
Click to collapse
Awesome im going to try it out tomorrow:good:
disregard
I been trying to get root on my grand x 3 but phone shuts off is unresponsive and have to pull battery to get phone to turn back on
cbc0201 said:
We now have full root!!
The latest version of Kingo for the PC will give you temp root. The link below will give you full root.
ZTE Write Protection problems solved (Simple)
http://androidforums.com/threads/zte-write-protection-for-zmax-and-other-zte-phones.1040331/
Works perfectly on the Grand X3
---------- Post added at 11:56 PM ---------- Previous post was at 11:34 PM ----------
Sent from my Z959 using XDA-Developers mobile app
Click to expand...
Click to collapse
I've achieved permanent root with this method, but, I'm having trouble replacing Kingo super user with SUPERSU. How were you able to do it?
Any one tried Link2SD yet since root is now working?
With this can we install custom roms? Or is that still a pipe dream right now?
---------- Post added at 04:49 PM ---------- Previous post was at 04:40 PM ----------
Also Im having issues. Usually there is a lot more help with this. It's explained a lot better. Can someone give me the steps to root? After that Im good on my own its the rooting process that I need a helmet and a short bus for
Hi, sorry if this is a stupid question, but I just noticed Sprint pushed an OTA for 6.0.1 to my stock rooted device (S-on) and I'm just trying to figure out what the best way to get this OTA is going to be. I'm assuming I shouldn't download and install the OTA as-is due to the TWRP recovery and root.
After looking around a bit, it seems like the only option available is to use a stock 6.0.0 RUU file in the bootloader and basically reset the entire device back to factory settings (losing all apps and data in the process presumably), installing the OTA, then re-flashing TWRP and re-rooting.
I guess what I'm asking is - 1. is this the correct way to go about doing this? and 2. is there any better alternative perhaps that doesn't involve losing my data?
Thanks in advance guys.
Been googling around for the last few days and scouring this board for just as long and still haven't come to a definitive conclusion. From what little I've seen the documentation on this seems kind of spotty and I'm just wondering which direction to head in. Any help on this would be much appreciated.
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Thanks for the reply, man.. Thats kind of what I had gathered pouring over all these articles and board posts. I went ahead and RUU'd back to 1.10.651.1 for sprint.. Literally just moments ago though I downloaded the OTA and hit install and got presented with an error screen during the update. Phone rebooted back into the system normally, and I went to check the version # only to see it unchanged, along with a prompt to install the OTA for 1.57.651.1 again.
Any idea why this might've happened or how to remedy it?
{
"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"
}
Wonders_Never_Cease said:
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Click to expand...
Click to collapse
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Wonders_Never_Cease said:
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Click to expand...
Click to collapse
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
txag2011 said:
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Click to expand...
Click to collapse
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Wonders_Never_Cease said:
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
Click to expand...
Click to collapse
Cool glad got it sorted...
txag2011 said:
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Click to expand...
Click to collapse
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Wonders_Never_Cease said:
Cool glad got it sorted...
Click to expand...
Click to collapse
First thing ya need to do is read how to install adb and fastboot and get away from toolkits... Download 2.67 from this thread...copy to device flash through twrp...
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
And didnt mean that in a snotty,sarcastic way... Those tools sometimes cause issues that could be avoided is all I was getting at...
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
I have to agree with Wonders_never_cease about the toolkits. I have used many different ones and they are great from a few things but not all things go right using them unlike adb/fastboot. You should have better results from using adb/fastboot here.
That being said.....it would be easier to achieve root by simply going to full stock using RUU or system/boot.img in fastboot, flashing TWRP, format data, reboot into TWRP, flash supersu 2.74 from your SD card either by itself to obtain normal root or follow steps here http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 for systemless root. it's that simple...or at least was for me. I never could get pushing supersu through adb right or to work really.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
Bond246 said:
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
Click to expand...
Click to collapse
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
mcbright80 said:
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
Click to expand...
Click to collapse
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Bond246 said:
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Click to expand...
Click to collapse
Ah so sorry, it was 4 am when i was replying so i missed that part on it installing correct, or confused it with the other question i was replying to at that same time haha......anyhoo....i looked for you as well and nothing was found on my end as well so I think you may be in the exact situation i was in when i bought the sprint variant of the A9. HTC has faults like all companies but the one that really pisses me off is their lack of proper support on ALL variants especially concerning firmware. The phone was released and i found NO RUU on their site or anywhere online and of course not many people had my specific variant which meant no one on here or anywhere had the means to get me the stock firmware i too needed to restore my phone.
The ONLY reason anyone here, who has SPRINT US VERSION, is able to then and NOW get the RUU on the HTC website is directly due to my incessant badgering and yelling at HTC damn near daily about having a handset on the market for sale but no firmware for it in case of tech service needs. You may have to do the same thing sadly.
I assume you have checked htc UK site for the rom downloads......contact their tech support and see whats up. Till then, like i had to when the sprint version came out....you'll have to just keep checking back on here and anywhere online for someone else who may post what you need or some other kind of solution.
Thanks mcbright80,
as you already said, HTC resists and says RUUs are only available in the US. I'm excited on their reaction that there are still lower RUU-versions of my UK-edition.
It is an annoying mess with all these different versions for tons of carriers, countrys and so on.
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.