Database Info

The first case reset Warranty Bit in Galaxy Note 3 Exynos N900 successfully!!!

Hello forum,
I come from Vietnam, I have participated in this forum for a long time. The devs helped guys like me so much to be able to use our phone in the best ways.
Today I have one thing to share with you, may be it will help the devs to find a way to solve the problem of reseting warranty bit in Samsung Galaxy Note 3 into 0.
I bought my Note 3 N900 five months ago. At that time, I rooted my phone and then update my note 3 via OTA. But from the fist update which showed Warranty Bit: 1 (MJ7). I didn't update it via OTA any more.
Then I download a stock rom named "STOCK-DEODEX-ROOT-N900XXUCMJ7_N900OLBCMJ3_N900DXUCMJ3_HOME" of developer @nguyenxuanhoa then rooted it again and used it untill yesterday.
Yesterday, I found that my device wasn't rooted and CWM disappear. I couldn't understand. Then I installed CWM and rooted it again. After that. I uploaded rom cook version 9.0 then 8.1 (android 4.4.2) of developer @nguyenxuanhoa but it did't work well (couldn't use apps restored from titanium backup and couldn't logged in evernote)
Then I used the stock Mj7 4 files but just uploaded 1 file AP in order to restore my phone to android 4.3 but it was suspended at samsung logo. Then I went to stock recovey to wipe data and reboot, but it was fault: force close samsung keyboard.
In the last time, I flashed 4 files in stock MJ7 to restore again and OMG! The warranty bit was restored to 0. I can't understand but very happy. I can use Knox, of course. Everything in my phone was restored as when i bought it from the seller.
I hope that information will help you to guess how could we resset warranty bit of Galaxy Note 3 N900 into 0.
Stock Rom Mj7 4 files: Link/
STOCK-DEODEX-ROOT-N900XXUCMJ7_N900OLBCMJ3_N900DXUCMJ3_HOME: Part 1 Part 2
Rom cook by @nguyenxuanhoa: Link
{
"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"
}
View attachment 2628353
View attachment 2628354

Maaaaaaaaaaaaaaaaan
if what you did is true and we can all do it.
then thank you very much my freind and hope that this will help the devs defeat this knox app.

We need someone to try this I hope that is true
Sent from my SM-N900

DON AMIGO said:
Maaaaaaaaaaaaaaaaan
if what you did is true and we can all do it.
then thank you very much my freind and hope that this will help the devs defeat this knox app.
Click to expand...
Click to collapse
dannycanrock said:
We need someone to try this I hope that is true
Sent from my SM-N900
Click to expand...
Click to collapse
I'm not sure, because there are not many people keep their N3 in firmware Mj7 like me, so I don't know if this case is right with the other. I just post my case there and hope that someone can follow this and reset warranty bit successfully, too.

ii have a note 2, i have full wipe and flashed 4 tar in bl, csc, ap and nothing happens, i still have knox bit 1, i am curious how did you do that, is it because you download bl then upload it agian? hummm

If you look a little the menu is a little different for n900 not like n9005.Maybe different bootloaders diferent knox and maybe for n900 work.

luckyboy_103 said:
I'm not sure, because there are not many people keep their N3 in firmware Mj7 like me, so I don't know if this case is right with the other. I just post my case there and hope that someone can follow this and reset warranty bit successfully, too.
Click to expand...
Click to collapse
Yeaahh, thanks for your report. We are working on testing progress. I think maybe the reason that you flash many time and get luck. I don't know how and why but good work.
Send from my SM-N900 using Tapatalk 4 Pre

newxdabie said:
ii have a note 2, i have full wipe and flashed 4 tar in bl, csc, ap and nothing happens, i still have knox bit 1, i am curious how did you do that, is it because you download bl then upload it agian? hummm
Click to expand...
Click to collapse
No, I just flashed AP file for the first time, then flashed all 4 files in stock mj7 for the second time and.. it worked :d
Sent from my SM-N900 using Tapatalk

will somebody test this method.

luckyboy_103 said:
No, I just flashed AP file for the first time, then flashed all 4 files in stock mj7 for the second time and.. it worked :d
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
Make a guide for amateur like us...
Sent from my SM-N900 using XDA Premium 4 mobile app

ghalib87 said:
Make a guide for amateur like us...
Sent from my SM-N900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe he got luck. Let's see how to do. Hope that's guide for developers to fix it perfect.
Send from my SM-N900 using Tapatalk 4 Pre

luckyboy_103 said:
No, I just flashed AP file for the first time, then flashed all 4 files in stock mj7 for the second time and.. it worked :d
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
I cant understand it... flashing ap before flash 4 files dont make any sense about it...because i realized that their flash bl first if you have knox bit the bl will load thia information and do not replace it...i guess there something is missing in your steps or because you flashed deox knox rom or rom with bl lower before...not sure

I can confirm this, However im not sure of the method. But I do remember It involved the MJ7 Firmware. At a point of flashing where my Phone got Soft Bricked, I noticed that the Warranty Bit was Reset and 0x0. At that Point the phone was not useable, and it was soft-bricked with a "Stuck on Boot Logo" Situation. However, After I installed CWM and SuperSu again, It was gone. In order to find out the exact method and to create a guide (And of course to take the bounty! ) I tried to recreate this over and over again, But It never worked out. Then I just ditched the idea thinking it might be a fault in the Recovery. Now that you have posted this in OP, I believe there is a trigger within the phone itself. The Phone which I tested too was a N900 and I was playing with the MJ7 Firmware.

newxdabie said:
I cant understand it... flashing ap before flash 4 files dont make any sense about it...because i realized that their flash bl first if you have knox bit the bl will load thia information and do not replace it...i guess there something is missing in your steps or because you flashed deox knox rom or rom with bl lower before...not sure
Click to expand...
Click to collapse
I can't understand, too. I flashed 4 files after flashing ap just because it was fault. There was nothing in my steps missed. I absolutely sure about that.
Sent from my SM-N900 using Tapatalk

JazonX said:
I can confirm this, However im not sure of the method. But I do remember It involved the MJ7 Firmware. At a point of flashing where my Phone got Soft Bricked, I noticed that the Warranty Bit was Reset and 0x0. At that Point the phone was not useable, and it was soft-bricked with a "Stuck on Boot Logo" Situation. However, After I installed CWM and SuperSu again, It was gone. In order to find out the exact method and to create a guide (And of course to take the bounty! ) I tried to recreate this over and over again, But It never worked out. Then I just ditched the idea thinking it might be a fault in the Recovery. Now that you have posted this in OP, I believe there is a trigger within the phone itself. The Phone which I tested too was a N900 and I was playing with the MJ7 Firmware.
Click to expand...
Click to collapse
Thank you for your confirmation. I am luckier than you while my phone was reset to 0x0 within any fault. I'm not sure it could happen again :d
Sent from my SM-N900 using Tapatalk

i'm sure that someone in this great forum will help us in this matter
and give us the method and hopefully help the devs here to defeat this knox app.

DON AMIGO said:
i'm sure that someone in this great forum will help us in this matter
and give us the method and hopefully help the devs here to defeat this knox app.
Click to expand...
Click to collapse
matbe downgrade between knox enable bootload can reset knox counter, i am in note 2 we have only 4.3 mk9, i ve doing this process lot of times and still knox bit =1 and i realized there are note 3 that have odin mode diffrent from yours, we have knox warrenty bit and ap swaev : A2, and your phone only has warenty bit, and tell me more one thing, when you flash the second time, you need turn indo odin mode(download mode) you already seeing knox bit = 0 this step or just after flashing 4 files? and what is your configuretion with odin? what version are you using? thx

newxdabie said:
matbe downgrade between knox enable bootload can reset knox counter, i am in note 2 we have only 4.3 mk9, i ve doing this process lot of times and still knox bit =1 and i realized there are note 3 that have odin mode diffrent from yours, we have knox warrenty bit and ap swaev : A2, and your phone only has warenty bit, and tell me more one thing, when you flash the second time, you need turn indo odin mode(download mode) you already seeing knox bit = 0 this step or just after flashing 4 files? and what is your configuretion with odin? what version are you using? thx
Click to expand...
Click to collapse
Regret that I didn't see warranty line when I flashed 4 files and even after that. I only saw it after flashing CWM failed as I mentioned in #1.
I just flashed files by odin normally. Version of odin is 3.04!

luckyboy_103 said:
Regret that I didn't see warranty line when I flashed 4 files and even after that. I only saw it after flashing CWM failed as I mentioned in #1.
I just flashed files by odin normally. Version of odin is 3.04!
Click to expand...
Click to collapse
so you flashed it dont in odin mode?, if you in odin mode you should see it

It mean that:
- flash 4.4.2 rom - > flash ap -> let's it boot in 20-30s -> wipe -> flash all 4 file (bootloader MJ7 again?) -> wipe
So, simply it can tell: Maybe a software bug in MJ7 bootloader that will check system integrity of system and set KNOX flag again to 0 (it was 1) in bootloader.
Why it's a bootloader bug? It didn't check check warranty bit was writen. It will check and rewrite everytime you flash it. (Maybe bootloader will check a flag/file in data/system/hidden partition that was set by kernel/OS that tell integrity state of system and set know flag)
So now i need a volunteer that have equal or below MJ7 (MJ1/MJ7)... And flash AP (MJ7) - when flash with odin please don't check reboot. when it flashed. Go to Recovery and wipe. Then flash 4 files include bootloader again.

(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

SM-G930T Root Doesn't Void Warranty

The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
This root works on all Marshmallow versions on Android on the T-Mobile S7
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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?