Database Info

SM-P905V Root. US Verizon

Updated to provide those things I have used to get to where I am. Original post is below the break.
I suppose I need to also add the normal blah, blah, blah. Do not attempt these things unless you are willing to brick your expensive tablet. Your choice to follow my recommendations or anyone else from this point forwards, are all on you.
I have a Verizon Samsung Galaxy Note 12.2 SM-P905V. Here is a screen shot showing my build info.
{
"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 have returned to stock per http://http://www.mediafire.com/download/dx...MULTI_CERT.zip Posted on kest874 thread http://forum.xda-developers.com/showthread.php?t=2795630. I have always taken the available carriers updates before rooting.
Next use Towelroot to allow root.
Towelroot is easily found if you search for it with any search engine. Towelroot is no longer supported by the dev who created it as he has moved on to bigger and better things.
I have never had to enter any code when using towelroot. I read where people need to input various character strings but not I. I can't explain any reasons why that is so.
Towelroot works great to root but! Capitalize the BUT! Do not allow KNOX to be disabled when Towelroot roots you and pops up a message about KNOX. That is what caused my hotbooting issue.
Download SuperSU from the play store and install.
Bingo, bango, bongo. Your rooted.
Now, if only I could get TWRP to ODIN without fail. Current version being attempted is 2.8.0.0.
------------------------------------------------------ Break ------------------------------------------------------------
I would like the tablet setup to be stable with root and a recovery. I am rooted now, towelroot, but there isn't a recovery available yet. I can wait for the recovery to become available but getting a stable root working is my number one issue.
Yes I am rooted but it isn't stable. My tablet reboots on a whim. Well actually I can continually duplicate the reboot. The reboot occurs exactly after I pull down the notification window after resuming the tablet from a timeout. I can tinker with anything I want on the tablet for as long as I want but if I let the screen timeout, poof. The tablet will suicide reboot exactly after screen wake and a notification window pull down.
With all that said, I odin'd back to new state last weekend. I let the tablet take all updates and I reinstalled all nonroot requiring apps from the store. I got a solid 5-6 days without any root on the tablet and not one single reboot.
Today I installed root through towelroot and I installed supersu. I specifically set my screen timeout to 30 seconds and waited 30 seconds to test the situation. Yuppers, after I pulled the notification window down it rebooted. I should add the tablet will suicide reboot also after opening a program and selecting something else, all after powering back up after a screen timeout. I continue to use the notification pull down as the example because it's stock and very, very easy to duplicate.
And it's not a normal reboot. It's like a partial reboot. What I witness the screen show, during a suicide reboot, is the Samsung logo with the spinning colors CCW and then the red Verizon splash screen. The boot completely bypasses the beginning boot screen that is individualized for the model and has the powered by android quip.
Does anyone have any ideas how to troubleshoot this further? TWRP doesn't have a recovery yet for this Verizon variant so any of that stuff is out of the question for now. I did install an ADB package on my Win7 machine and I'm able to list the device.
Best Regards
Shon

Sounds similar to the bug with notification shade while using chromecast when the volume and brightness sliders are on in the notification panel. If yours are enabled try turning them off. Probably won't help but worth a shot.
Sent from my SM-P900 using Tapatalk

muzzy996 said:
Sounds similar to the bug with notification shade while using chromecast when the volume and brightness sliders are on in the notification panel. If yours are enabled try turning them off. Probably won't help but worth a shot.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Heck it's worth investigating. I investigated. No change. Oh well, thanks for the suggestion though. One never knows how simple the issue might be.

Rename?
Are my difficulties possibly due to both TWRP and CF auto-root files named as viennaltexx vs viennaltevzw? Android system info program shows my device as viennaltevzw.
BTW I wiped again to try CF auto-root through odin with a fresh install. All still fails in odin during the nand write start. Same as TWRP.
Just wondering if the problem could be as simple as renaming the files.

Hello? *tap, *tap, *tap.
*blows into microphone.
Testing, testing, one. Two. Three.
Is this thing on?
LOL.
Didn't want to just do a simple bump.

Based on the lack of response I assume you're the only 905v user experiencing this so it leads me to suspect a certain software installed that is causing it, perhaps one that pushes a persistent notification. I don't know. The other thought is to go into developer options and tinker with turning off animations or forcing gpu rendering or disabling hardware overlays.
Sent from my SM-P900 using Tapatalk

Perfect. Thank you muzz. I will report back.

I have a 905V, rooted and tons of Xposed applets installed, don't have the issue.

Yea I have to have something strange going on. Also the fact that I can't load TWRP or CF-auto root because I fail at the nand write start. I know my nand isn't corrupt because I can odin the base image, but one problem at a time.
td - yes, Xposed. That is what I want to get to, but I need to get through this rebooting issue first.
Thanks guys

Someone has twrp?
I have P905v (verizon) and only root via towel root method, which worked fine. I too have a bunch of xposed modules and they work fine.
If anyone had twrp with the p905v, can you tell me where you got it from?
Sent from my SM-P905V using XDA Free mobile app

Gonkulor said:
I have a Verizon Samsung Galaxy Note 12.2 SM-P905V. Here is a screen shot showing my build info.
View attachment 2890423
I would like the tablet setup to be stable with root and a recovery. I am rooted now, towelroot, but there isn't a recovery available yet. I can wait for the recovery to become available but getting a stable root working is my number one issue.
Yes I am rooted but it isn't stable. My tablet reboots on a whim. Well actually I can continually duplicate the reboot. The reboot occurs exactly after I pull down the notification window after resuming the tablet from a timeout. I can tinker with anything I want on the tablet for as long as I want but if I let the screen timeout, poof. The tablet will suicide reboot exactly after screen wake and a notification window pull down.
With all that said, I odin'd back to new state last weekend. I let the tablet take all updates and I reinstalled all nonroot requiring apps from the store. I got a solid 5-6 days without any root on the tablet and not one single reboot.
Today I installed root through towelroot and I installed supersu. I specifically set my screen timeout to 30 seconds and waited 30 seconds to test the situation. Yuppers, after I pulled the notification window down it rebooted. I should add the tablet will suicide reboot also after opening a program and selecting something else, all after powering back up after a screen timeout. I continue to use the notification pull down as the example because it's stock and very, very easy to duplicate.
And it's not a normal reboot. It's like a partial reboot. What I witness the screen show, during a suicide reboot, is the Samsung logo with the spinning colors CCW and then the red Verizon splash screen. The boot completely bypasses the beginning boot screen that is individualized for the model and has the powered by android quip.
Does anyone have any ideas how to troubleshoot this further? TWRP doesn't have a recovery yet for this Verizon variant so any of that stuff is out of the question for now. I did install an ADB package on my Win7 machine and I'm able to list the device.
Best Regards
Shon
Click to expand...
Click to collapse
OK so I posted the following message in another forum because I couldn't find this one again. Someone kindly provided me with the link back here so I wanted to post this again, but here. Please advise if any others have this issue or have a shot at a solution.
"I rooted with a towel root and downloaded from the link provided in the first post. I clicked the "make it ra1n" button and received a message stating you are now rooted, please enjoy. I Installed SU (pro version) by chainsfire from playstore, updated binary using "normal" method and used root checker. It confirmed root access and then it was on to Titanium Backup Pro.
Here is my main issue though. Almost immediately after rooting with this method via the provided link, my P905V started Hot Rebooting itself almost every time i attempt to wake it. Flashed back to stock and started all over. Same thing, clicked "make it ra1n" once and received confirmation of root, installed SU again, did root checker and it confirmed root. It again started hot rebooting upon wake up. It did not do it once on the original firmware, nor when i reflashed before rooting with towel root. I noticed someone else had this issue in another thread but received minimal feedback and nobody else with this issue.
My question, is anyone else having this issue? Anyone know where i should start to determine the cause here? I do not have enough posts to post in the development forums even though i have been a member for some time. I am very familiar with root and the Galaxy Note product line, but I am stumped. I have solved all other issues by reading through posts and finding solutions. This is the first time I am totally lost. All help or suggestions welcome. Thanks."

aburns7487 said:
Someone has twrp?
I have P905v (verizon) and only root via towel root method, which worked fine. I too have a bunch of xposed modules and they work fine.
If anyone had twrp with the p905v, can you tell me where you got it from?
Sent from my SM-P905V using XDA Free mobile app
Click to expand...
Click to collapse
Well I also get those reboots in my p907a att model.

torreon901 said:
Well I also get those reboots in my p907a att model.
Click to expand...
Click to collapse
After rooting with towelroot?

bbro84 said:
After rooting with towelroot?
Click to expand...
Click to collapse
Had same issue after towel root on AT&T p907a resolved it by factory resetting it then re rooting and leaving Knox active.

cnote74 said:
Had same issue after towel root on AT&T p907a resolved it by factory resetting it then re rooting and leaving Knox active.
Click to expand...
Click to collapse
I did reflash once, i wil give factory reset and not freezing Knox. thanks for the suggestion and I will let you know if it works.

bbro84 said:
I did reflash once, i wil give factory reset and not freezing Knox. thanks for the suggestion and I will let you know if it works.
Click to expand...
Click to collapse
Thanks I will do same thing....
---------- Post added at 05:43 AM ---------- Previous post was at 05:42 AM ----------
bbro84 said:
After rooting with towelroot?
Click to expand...
Click to collapse
Yes... after towelroot

aburns7487 said:
Someone has twrp?
I have P905v (verizon) and only root via towel root method, which worked fine. I too have a bunch of xposed modules and they work fine.
If anyone had twrp with the p905v, can you tell me where you got it from?
Sent from my SM-P905V using XDA Free mobile app
Click to expand...
Click to collapse
Here is the TWRP suggested for the P905V http://forum.xda-developers.com/showpost.php?p=54299636&postcount=280
I'm not having luck getting it to stick via odin. maybe you could have better results.

bbro84 said:
OK so I posted the following message in another forum because I couldn't find this one again. Someone kindly provided me with the link back here so I wanted to post this again, but here. Please advise if any others have this issue or have a shot at a solution.
"I rooted with a towel root and downloaded from the link provided in the first post. I clicked the "make it ra1n" button and received a message stating you are now rooted, please enjoy. I Installed SU (pro version) by chainsfire from playstore, updated binary using "normal" method and used root checker. It confirmed root access and then it was on to Titanium Backup Pro.
Here is my main issue though. Almost immediately after rooting with this method via the provided link, my P905V started Hot Rebooting itself almost every time i attempt to wake it. Flashed back to stock and started all over. Same thing, clicked "make it ra1n" once and received confirmation of root, installed SU again, did root checker and it confirmed root. It again started hot rebooting upon wake up. It did not do it once on the original firmware, nor when i reflashed before rooting with towel root. I noticed someone else had this issue in another thread but received minimal feedback and nobody else with this issue.
My question, is anyone else having this issue? Anyone know where i should start to determine the cause here? I do not have enough posts to post in the development forums even though i have been a member for some time. I am very familiar with root and the Galaxy Note product line, but I am stumped. I have solved all other issues by reading through posts and finding solutions. This is the first time I am totally lost. All help or suggestions welcome. Thanks."
Click to expand...
Click to collapse
That Sir. is exactly my problem too. Not that I am glad to find someone else with the same problem, but maybe we can figure this out.
I just did another wipe. I still haven't installed towelroot yet.

cnote74 said:
Had same issue after towel root on AT&T p907a resolved it by factory resetting it then re rooting and leaving Knox active.
Click to expand...
Click to collapse
I swear I tried this but I have wiped so many times I don't know. I might as well try it too.

Gonkulor said:
I swear I tried this but I have wiped so many times I don't know. I might as well try it too.
Click to expand...
Click to collapse
Can anyone who is having this issue verify if they have knox frozen or uninstalled? Here is why; I opened Titanium Backup, searched for "knox" and found only two of four frozen knox items. I froze the other two knox related items and have not had the hot reboot issue occur sinve. Granted it has only been about 12 hours and I was not using the tablet for several of those hours.
I am hoping others who are having this issue can step in and confirm if they too only froze some of the knox items or if this has nothing to do with knox. If my issue is fixed and not because of the knox stuff, then a solution is useless since I still don't know what caused the issue. Thanks to all for the input.
---------- Post added at 10:10 AM ---------- Previous post was at 10:03 AM ----------
bbro84 said:
Can anyone who is having this issue verify if they have knox frozen or uninstalled? Here is why; I opened Titanium Backup, searched for "knox" and found only two of four frozen knox items. I froze the other two knox related items and have not had the hot reboot issue occur sinve. Granted it has only been about 12 hours and I was not using the tablet for several of those hours.
I am hoping others who are having this issue can step in and confirm if they too only froze some of the knox items or if this has nothing to do with knox. If my issue is fixed and not because of the knox stuff, then a solution is useless since I still don't know what caused the issue. Thanks to all for the input.
Click to expand...
Click to collapse
EDIT: It just hot rebooted so scratch the above idea...back to drawing board.

(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"???

Update arrived!

I am downloading an update that is 568.3 mb. GO GRAB 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"
}

Me too!
Manually went to update...

Update finally
AT LAST
Got it!!

5.1.1?

Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671

wildjeep said:
Pump your brakes
If this is the 5.1.1 update and you are rooted and enjoy a custom device. Please understand what this update means before flashing it.
http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
Click to expand...
Click to collapse
You are 100% correct my friend... I hate when people hurry up and jump on the update, then complain non stop they lost root and can't get it back....
Sent from my SM-G925V using Xparent Green Tapatalk 2

Soooperstar said:
5.1.1?
Click to expand...
Click to collapse
+1

If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1

If anyone has taken the update, please report back on whether TWRP and/or Cf autoroot works

Sent from my SM-G925P using Tapatalk

dhonzik said:
If you upgrade to 5.1.1, you will not be able to root at this time
DO NOT ATTEMPT TO ROOT
I have been unsuccessful to go back to OE2 via odin, does someone have the recovery image for 5.1.1
Click to expand...
Click to collapse
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:

I will say, however, the device seems to run much smoother and early signs show battery improvement as well. Obviously it's early but it seems promising. Just wanted to share my stock experience as I chose to not root for the future payment platform

I updated but I am not root
no ram management .

If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?

Alpine- said:
If you take this update, you cannot root for the time being and certainly cannot Safe root (not tripping knox) with PingPoint root. In addition, you cant downgrade kernel, etc.
So the question becomes, what is the best course of action here. Can we PingPong root prior build, then update to OF7 kernel and rom once someone repacks them? Flash with FlashFire and maintain root? Then again, I guess we could accept the OTA and stay stock until CF-Auto Root is updated to work with it.
Either way, I'm holding for a bit here to see what shakes out...
UPDATE: thought about this a second. Sprint doesnt typically lock boot loader like AT&T, verizon. So this locked boot loader is whats preventing people from downgrading kernel once they update right? So this should not be an issue with Sprint if the boot loader is not locked?
Click to expand...
Click to collapse
Take a look at this thread: http://forum.xda-developers.com/sprint-galaxy-s6-edge/help/dont-odin-5-1-1-t3136671
It is not a looked boot loader that is the problem. T-Mobile solved it so I am sure it will be solved for us very soon.

wildjeep said:
This is one of the compilations that has been warned for a few weeks now. It will take some time to achieve a stable Root/Recovery.
So if anyone is satisfied with stock. Unroot and flash away.
Or sit tight and wait for the custom development to catch up to the current stock software :highfive:
Click to expand...
Click to collapse
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.

dhonzik said:
Heads up the t-mobile TWRP recovery does get my bricked phone to the recovery, but the buttons do not work. If it did I had a backup I would have tried. Heading to the Sprint Store Tech Center to hopefully get a working phone or a replacement.
Click to expand...
Click to collapse
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery

Soooperstar said:
So did the Sprint recovery not work?
How did you brick?
Sprint may not mess with it once the see the wrong recovery
Click to expand...
Click to collapse
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.

dhonzik said:
It was attempt to see if the CF Auto-Root would work after the update. I went back to other recovery that doesn't open up, if the tech center has the complete firmware maybe it will be to flash it back on. I opened a thread to see if someone can pull the stock recovery from the update. Trying to reflash back to OE2 fails.
Click to expand...
Click to collapse
Did you try to Odin our twrp?

Soooperstar said:
Did you try to Odin our twrp?
Click to expand...
Click to collapse
Yes, it was a no go, $75 later I'll have a new phone in a week

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.

Root?

Is the zs551kl officially bootloader-unlockable and able to be rooted?
If that's the case, it would mean it's a much better phone than many of the latest flagships: sdcard, jack, FM radio, dual SIM, larger battery, stereo speakers, more complete GPS, good resolution screen, etc.

I haven't seen anything yet, but I assume it's coming. I don't think there will be a lot of roms though.

Let's pray that someone popup with that

rblanca said:
Let's pray that someone popup with that
Click to expand...
Click to collapse
Have you got this device? There is aTWRP available, but I'm not sure if anyone has successfully rooted, etc.

temporarium said:
Have you got this device? There is aTWRP available, but I'm not sure if anyone has successfully rooted, etc.
Click to expand...
Click to collapse
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader....but ASUS has made public the app to unlock the bootloader.
---------- Post added at 11:41 PM ---------- Previous post was at 11:33 PM ----------
temporarium said:
Have you got this device? There is aTWRP available, but I'm not sure if anyone has successfully rooted, etc.
Click to expand...
Click to collapse
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader neither install TWRP ....but ASUS has made public the app to unlock it.

rblanca said:
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader....but ASUS has made public the app to unlock the bootloader.
Click to expand...
Click to collapse
Have you tried this?
https://forum.xda-developers.com/zenfone-4-pro/development/recovery-twrp-3-1-1-0-zs551kl-t3692186
All you need is a way to flash root.

rblanca said:
Yes I have it....but currently there isnt any modded kernel with root enabled or any rom...so there is no point on unlock the bootloader....but ASUS has made public the app to unlock the bootloader.
Click to expand...
Click to collapse
Out of curiosity, what made you choose this phone over all the others? How do you like it so far? Pros\cons?

temporarium said:
Have you tried this?
https://forum.xda-developers.com/zenfone-4-pro/development/recovery-twrp-3-1-1-0-zs551kl-t3692186
All you need is a way to flash root.
Click to expand...
Click to collapse
No, because , like I said before...until we have a Rooted kernel available to download or a custom rom to install there is no point on install TWRP or unlock the bootloader....I'm pretty sure that in the next months there are going to be Roms and Custom Kernels (Rooted), it's too soon the phone was released on October (the past month).
About what made me chose this phone...it was
- Unlockeable Bootloader
- Snapdragon 835 as CPU
- 6 GB of Ram
- Good camera
- ASUS it's a good brand.
- FM raido
The phone its pretty damn fast...multitasking is amaizing...the battery dont seems so well like my, now broken, LG G5 but at least it runs for 1 day and a few hours but maybe its due the "new phone effect" (you play with it more the first days of use XD)

Magisk should give you root as long as bootloader can be unlocked.
I'll watch this space for root as I'm about to go get one myself because Snapdragon 835, then I have 15 days to test it on one game to decide whether to keep or return, lol.

motopig said:
Magisk should give you root as long as bootloader can be unlocked.
I'll watch this space for root as I'm about to go get one myself because Snapdragon 835, then I have 15 days to test it on one game to decide whether to keep or return, lol.
Click to expand...
Click to collapse
That's what I thought: once you unlock the bootloader and ADB-flash TWRP, you should be able to install SuperSU or Magisk (with corresponding manager app) and be good to go. So please test and let us know if you can.

temporarium said:
That's what I thought: once you unlock the bootloader and ADB-flash TWRP, you should be able to install SuperSU or Magisk (with corresponding manager app) and be good to go. So please test and let us know if you can.
Click to expand...
Click to collapse
Sorry to disappoint you but I'm not going to unlock my bootloader right now....the reason the phone its new (and expensive), there isn't a single rom to install or kernel to flash (on my LG G5 you have to flash another kernel in order to have root, but maybe that has change).
More importante there isnt any unbrick guide yet if something fails plus my phone it's not being selled on my country so there isn't any kind of warranty or repair service if something fails. WIth 6gb of ram I can deal with some ASUS apps pre installed so I dont need to root it right now.
But like a said before...its a great phone...damn faster one! i'll recommend it.

Even if one wanted to unlock the bootloader to try things out, it is not possible right now anyway.
Tried it with Asus' official unlock app (just got the phone today! :victory, and the app simply crashes before it even gets to talk to the bootloader, so there is currently no way to do it. Fastboot still reports the device as locked.
Maybe I should have tried it before applying the latest OTA update, but oh well!
rblanca has a point though, with no way to restore the phone should something go seriously wrong, I won't try any more exotic methods to try to crack open that bootloader at the moment either. The various guides that float around on the web look dangerous at best.

rblanca said:
Sorry to disappoint you but I'm not going to unlock my bootloader right now....the reason the phone its new (and expensive), there isn't a single rom to install or kernel to flash (on my LG G5 you have to flash another kernel in order to have root, but maybe that has change).
More importante there isnt any unbrick guide yet if something fails plus my phone it's not being selled on my country so there isn't any kind of warranty or repair service if something fails. WIth 6gb of ram I can deal with some ASUS apps pre installed so I dont need to root it right now.
But like a said before...its a great phone...damn faster one! i'll recommend it.
Click to expand...
Click to collapse
I understand your concern. No worries!

damnaliens said:
Even if one wanted to unlock the bootloader to try things out, it is not possible right now anyway.
Tried it with Asus' official unlock app (just got the phone today! :victory, and the app simply crashes before it even gets to talk to the bootloader, so there is currently no way to do it. Fastboot still reports the device as locked.
Maybe I should have tried it before applying the latest OTA update, but oh well!
rblanca has a point though, with no way to restore the phone should something go seriously wrong, I won't try any more exotic methods to try to crack open that bootloader at the moment either. The various guides that float around on the web look dangerous at best.
Click to expand...
Click to collapse
We'll just have to sit tight.

Root!
Good news!
Asus fixed the unlock app ( https://www.asus.com/de/Phone/ZenFone-4-Pro-ZS551KL/HelpDesk_Download/ ) and bumped it to version 9.1.0.0
It now successfully unlocks the device's bootloader. I went ahead and did it since I already voided my warranty when trying to unlock it with the previous, bugged version anyway.
Works fine, fastboot reports the bootloader as unlocked. Device contents got factory-wiped as per announced in the app, so make sure to back up your things if you wanna do it. :silly:
Edit:
Aaaaand rooted with Magisk.
{
"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 installing TWRP I just followed this guide here: https://forum.xda-developers.com/ze...ide-how-to-root-acces-magisk-manager-t3678678
Applies 1:1 to the Zenfone 4 Pro as well and worked flawlessly. :fingers-crossed:

Nice work! Does Android Pay work with magisk on this phone?

@bahua78
Android Pay isn't available in my country yet, so I can't test this. Maybe somebody else can find out. :0

Is it possible to update firmware via a memory card with root?