Related
Hoping some kind soul will take a few minutes to get me up to speed on what I need to know about hacking the M8.
I am not a total newb, and have lingered around XDA for a while. I've rooted many phones and tablets, even worked with cooking my own ROMS for android and older winmo 4+ years ago. I've just not been involved in the scene and am just about to get my new M8 and would like a crash course.
I really don't mind reading - so if someone has a great all-in-one guide they recommend, I'll certainly start with that...its just the endless searching for the up-to-date info I'm looking to avoid. I actually prefer to understand what I'm doing rather than just click "unlock"
Top most questions in my mind:
1) The biggest thing I would like to know to start is the best way to backup/up protect my device before I do anything to it.
I'd like to be able to return it to total stock (minus any impossibility in re-locking a bootloader) in case I mess things up or need to return, etc.
2) Current best methods for rooting, unlocking, etc. I just want to make sure I'm not doing something out of date that might be more effort than necessary/dangerous.
3) I see this new TWRP thing...which looks like an alternate to CWM. Which is better for me to use for M8?
4) Any M8 specific big dangers to watch out for to prevent bricking.
I always look to XDA for the best advice, but sometimes the site is difficult to navigate to find the most clear explanation.
TIA!
TraderJack said:
Hoping some kind soul will take a few minutes to get me up to speed on what I need to know about hacking the M8.
I am not a total newb, and have lingered around XDA for a while. I've rooted many phones and tablets, even worked with cooking my own ROMS for android and older winmo 4+ years ago. I've just not been involved in the scene and am just about to get my new M8 and would like a crash course.
I really don't mind reading - so if someone has a great all-in-one guide they recommend, I'll certainly start with that...its just the endless searching for the up-to-date info I'm looking to avoid. I actually prefer to understand what I'm doing rather than just click "unlock"
Top most questions in my mind:
1) The biggest thing I would like to know to start is the best way to backup/up protect my device before I do anything to it.
I'd like to be able to return it to total stock (minus any impossibility in re-locking a bootloader) in case I mess things up or need to return, etc.
2) Current best methods for rooting, unlocking, etc. I just want to make sure I'm not doing something out of date that might be more effort than necessary/dangerous.
3) I see this new TWRP thing...which looks like an alternate to CWM. Which is better for me to use for M8?
4) Any M8 specific big dangers to watch out for to prevent bricking.
I always look to XDA for the best advice, but sometimes the site is difficult to navigate to find the most clear explanation.
TIA!
Click to expand...
Click to collapse
1) The best most efficient way of backing up your device is to make a Nandroid backup with a recovery such as CWM or TWRP, but of course there will always be times where you could do something simpler to solve your problem such as disabling the Xposed framework but how? My phone is stuck in a bootloop, how would I disable it? The answer is when installing the framework make sure to first in the settings select to create flashable zips (manual) then once they are created go back and do the 'Classic' method. Now I'm sure if you're as new as you say you are you most likely don't know what Xposed is, it is a separate framework which allows you to customize your ROM to do things similar to what a 'Custom' ROM would normally always do. Most people don't think before installing these modules and end up soft-bricking their device and have to use their Nandroids to restore them but the way I mentioned is far simpler.
2) The utmost best method currently available (and only available) for rooting, unlocking, S-OFF & etc is currently Sunshine, you can read up about it here. Sadly and or not so sadly it costs $25 per device but it will do everything you will need to get started such as S-OFF (Security OFF, S-ON prevents writing to the /system partition and some other things I can't remember), Bootloader unlock & root.
3) Personally I prefer TWRP because it just feels like it has more ease of use towards it but thats just my opinion. There is an alternative to it which is CWM as you mentioned or 'PhilZ' CWM, Philz CWM is a touch-based version which to my experiences is a bit buggy but it works. I personally recommend TWRP but you might as well play around with them and see which one you like best.
4) Biggest danger of them all: To my knowledge that is, attempting to revert to S-ON. That is the most dangerous thing I am aware of at the moment but there may be something more dangerous but from what I know that is the most risky thing that is HTC based and or anything based.
This can be considered a good "All in one guide" for you to follow, it has pretty much everything I can think of at the moment.
An alternative to that one would be this one excluding all of the stuff involving Weaksauce and Firewater as Firewater does not work on newer devices and already rooted users don't have a use for Weaksauce. Still though it's a good tutorial for flashing a recovery and rooting.
Here is a solid tutorial on how to revert to stock if you ever decide to (once more do NOT attempt S-ON).
& if you're interested in using ROM's for other carrier variants of your phone then this one may be of interest to you.
Lastly, if you're concerned about any warranty things then as long as you do an RUU like the one mentioned in the 'Reverting to Stock' thread you will have no problems with it even if you're bootloader is unlocked and you're S-OFF. Why you may be wondering?? HTC sometimes ships phones already S-OFF/Bootloader unlocked and also I sort of think they just don't really care... you know as long as you didn't mess the phone up.
-----------------------------------------------------
If you have any further questions, I left something unclear or you just need me to elaborate further on something then feel free to ask further questions and I recommend doing your own research on these things before attempting them. Good luck and happy modding!
TraderJack said:
Hoping some kind soul will take a few minutes to get me up to speed on what I need to know about hacking the M8.
I am not a total newb, and have lingered around XDA for a while. I've rooted many phones and tablets, even worked with cooking my own ROMS for android and older winmo 4+ years ago. I've just not been involved in the scene and am just about to get my new M8 and would like a crash course.
I really don't mind reading - so if someone has a great all-in-one guide they recommend, I'll certainly start with that...its just the endless searching for the up-to-date info I'm looking to avoid. I actually prefer to understand what I'm doing rather than just click "unlock"
Top most questions in my mind:
1) The biggest thing I would like to know to start is the best way to backup/up protect my device before I do anything to it.
I'd like to be able to return it to total stock (minus any impossibility in re-locking a bootloader) in case I mess things up or need to return, etc.
2) Current best methods for rooting, unlocking, etc. I just want to make sure I'm not doing something out of date that might be more effort than necessary/dangerous.
3) I see this new TWRP thing...which looks like an alternate to CWM. Which is better for me to use for M8?
4) Any M8 specific big dangers to watch out for to prevent bricking.
I always look to XDA for the best advice, but sometimes the site is difficult to navigate to find the most clear explanation.
TIA!
Click to expand...
Click to collapse
The above post about covers it. Only thing I would like to add is I much prefer Phil's touch recovery based on CMW and try firewater method for soft and unlocking boot loader before paying for sunshine. It may or may not work. But could possibly save you the cash.
mdorrett said:
The above post about covers it. Only thing I would like to add is I much prefer Phil's touch recovery based on CMW and try firewater method for soft and unlocking boot loader before paying for sunshine. It may or may not work. But could possibly save you the cash.
Click to expand...
Click to collapse
Philz recovery is amazing, have you used the M8 unified builds yet? Or are you still sticking to the last Verizon build?
Sent from my HTC6525LVW using Tapatalk
Thanks all. I will certainly read up on what you've written and follow up with any questions I may have.
So I read a little bit on the posts above... Ick...when I was deciding on the M8 I checked to see if it was all hackable and apparently found the positive information for only the old methods and didn't realize a $25 price tag was the *only* way to really unlock the phone.
I mean...I don't totally begrudge the devs charging for it...but honestly I've never heard of this before in the 8-10 years I've been modding with smartphones of charging for this. While $25 may be nothing compared to a $700 unlocked phone, it sure is a heck of a lot more than $0, which was where the previous bar was set. You'd think $5 or $10 would be a better place to start.
Of course, it doesn't look like I have any other option though. I do have some more questions:
1) What are the pieces that sunshine does that can't be done elsewhere? It looks like there are several root methods - so is sunshine the only way to S-OFF or is it also the only way to unlock the bootloader?
2) If I don't do sunshine, and therefore can't S-OFF (and maybe can't unlock bootloader), can I still root? If so, is it only a temp unroot? And is there really a downside to that?
3) In all honesty, while I'd like to have everything unlocked, I think I will be happy with a root for now if that's enough to do some hacks (like maybe energy saving and wifi tether, etc.). Will I be able to do those with just root? I'm not really clear on the actual purpose of the S-OFF vs. the unlocked boot loader. Maybe in a few months I will be tired of the stock ROM and cough up the dough.
4) In order to do the backups to revert to stock, what steps must I first obtain and can I do those steps for free (aka no Sunshine) and are they reversible? IOW, what's the minimum I must "hack" the device in order to get a stock backup and/or to recover it.
Finally - when did the "firewater" method stop working? Is it newer hardware being shipped or a certain firmware/OS level update that blocked it? It sounds pretty unlikely that it will work for a new phone, but it won't hurt to try if it doesn't, right?
thanks again for the jump start....I think just jumping in and doing is the best way to learn, but I don't want to leap without protecting myself at the outset.
TraderJack said:
So I read a little bit on the posts above... Ick...when I was deciding on the M8 I checked to see if it was all hackable and apparently found the positive information for only the old methods and didn't realize a $25 price tag was the *only* way to really unlock the phone.
I mean...I don't totally begrudge the devs charging for it...but honestly I've never heard of this before in the 8-10 years I've been modding with smartphones of charging for this. While $25 may be nothing compared to a $700 unlocked phone, it sure is a heck of a lot more than $0, which was where the previous bar was set. You'd think $5 or $10 would be a better place to start.
Of course, it doesn't look like I have any other option though. I do have some more questions:
1) What are the pieces that sunshine does that can't be done elsewhere? It looks like there are several root methods - so is sunshine the only way to S-OFF or is it also the only way to unlock the bootloader?
2) If I don't do sunshine, and therefore can't S-OFF (and maybe can't unlock bootloader), can I still root? If so, is it only a temp unroot? And is there really a downside to that?
3) In all honesty, while I'd like to have everything unlocked, I think I will be happy with a root for now if that's enough to do some hacks (like maybe energy saving and wifi tether, etc.). Will I be able to do those with just root? I'm not really clear on the actual purpose of the S-OFF vs. the unlocked boot loader. Maybe in a few months I will be tired of the stock ROM and cough up the dough.
4) In order to do the backups to revert to stock, what steps must I first obtain and can I do those steps for free (aka no Sunshine) and are they reversible? IOW, what's the minimum I must "hack" the device in order to get a stock backup and/or to recover it.
Finally - when did the "firewater" method stop working? Is it newer hardware being shipped or a certain firmware/OS level update that blocked it? It sounds pretty unlikely that it will work for a new phone, but it won't hurt to try if it doesn't, right?
thanks again for the jump start....I think just jumping in and doing is the best way to learn, but I don't want to leap without protecting myself at the outset.
Click to expand...
Click to collapse
1) sunshine is the only way to s-off if firewater doesn't work. It pushes an exploit that turns the secure flag off so s-off is achieved, then it pushes a separate exploit to unlock the bootloader. You may be able to change your phone carrier ID so htc dev can s-off your phone, but it doesn't do everything sunshine does.
2) without using sunshine you can still have temporary root with weaksauce, but it's really limited. Since your phone is still s-on, it isn't able to write to the system partition. It means you lose root on every reboot, and you have to wait up to a minute for weaksauce to root again.
Also without an unlocked bootloader you are unable to flash a custom recovery, which means you can't make a nandroid. Not having a nandroid sucks because if you soft brick your phone you have no choice but to go completely back to stock. Not a great situation to be in.
Any root framework or application that requires modification of your system folder won't work.
There's no question paying $25 for sunshine is worth it.
3) here's the some definitions:
S-on = security flag on, system write protected
S-off = security flag off, system write enabled
Unlocked bootloader: ability to flash custom kernels and Recoveries.
Having access to a custom recovery is everything. Allows easy backup capabilities in case a rom modification goes bad. Allows super user permissions to be flashed directly into the system partition to allow permanent root. And gives you the ability to keep an unlocked bootloader without worry that Verizon will patch the current exploit.
Even on a stock rom it's worth it to have an unlocked bootloader. The modifications you're referring to require a custom recovery, and even if you could install them without it, it's still recommended to have a nandroid available in case your phone doesn't boot afterwards. I'm still running stock myself.
4) getting back to stock isn't easy. Verizon or HTC didn't release an official ruu. You'd have to flash the unofficial ruu, then turn your flags back to S-on, and hope it doesn't detect anything weird and flag your phone as tampered. The information was already linked to you in earlier posts, you just have to read up on it.
5) firewater stopped working on newer hardware versions, has nothing to do with firmware versions. There's no harm in trying it, but it most likely won't work on a new phone.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
1) sunshine is the only way to s-off if firewater doesn't work. It pushes an exploit that turns the secure flag off so s-off is achieved, then it pushes a separate exploit to unlock the bootloader. You may be able to change your phone carrier ID so htc dev can s-off your phone, but it doesn't do everything sunshine does.
2) without using sunshine you can still have temporary root with weaksauce, but it's really limited. Since your phone is still s-on, it isn't able to write to the system partition. It means you lose root on every reboot, and you have to wait up to a minute for weaksauce to root again.
Also without an unlocked bootloader you are unable to flash a custom recovery, which means you can't make a nandroid. Not having a nandroid sucks because if you soft brick your phone you have no choice but to go completely back to stock. Not a great situation to be in.
Any root framework or application that requires modification of your system folder won't work.
There's no question paying $25 for sunshine is worth it.
3) here's the some definitions:
S-on = security flag on, system write protected
S-off = security flag off, system write enabled
Unlocked bootloader: ability to flash custom kernels and Recoveries.
Having access to a custom recovery is everything. Allows easy backup capabilities in case a rom modification goes bad. Allows super user permissions to be flashed directly into the system partition to allow permanent root. And gives you the ability to keep an unlocked bootloader without worry that Verizon will patch the current exploit.
Even on a stock rom it's worth it to have an unlocked bootloader. The modifications you're referring to require a custom recovery, and even if you could install them without it, it's still recommended to have a nandroid available in case your phone doesn't boot afterwards. I'm still running stock myself.
4) getting back to stock isn't easy. Verizon or HTC didn't release an official ruu. You'd have to flash the unofficial ruu, then turn your flags back to S-on, and hope it doesn't detect anything weird and flag your phone as tampered. The information was already linked to you in earlier posts, you just have to read up on it.
5) firewater stopped working on newer hardware versions, has nothing to do with firmware versions. There's no harm in trying it, but it most likely won't work on a new phone.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
It also seems that firewater has nothing to do with hardware versions either. As I have a buddy with same hardware versions as me and FW worked perfectly. I am not exactly sure why FW works for some and not others.
---------- Post added at 08:07 AM ---------- Previous post was at 08:06 AM ----------
Also as far as changing CID I have not found a way to do this with out having S-Off already. If there is one please point me in the right direction. Thank you!
mdorrett said:
It also seems that firewater has nothing to do with hardware versions either. As I have a buddy with same hardware versions as me and FW worked perfectly. I am not exactly sure why FW works for some and not others.
---------- Post added at 08:07 AM ---------- Previous post was at 08:06 AM ----------
Also as far as changing CID I have not found a way to do this with out having S-Off already. If there is one please point me in the right direction. Thank you!
Click to expand...
Click to collapse
I guess I meant hardware variation, not version, it's not something you can simply check, but the internals of each phone is different. If htc used different manufacturers for the same internals it'll break firewater. The hardware version number would look the same.
Sent from my HTC6525LVW using Tapatalk
So I've read up on a good bit of what you've all posted - again thanks for that.
My M8 will be here tomorrow and I plan to use it for a few days without any tampering to ensure that I like the phone and that the reception in my home is adequate (problem had on my last upgrade attempt a year ago to a Razr M with Verizon). If all looks good, I will attempt the firewater method this weekend. If unsuccessful, I think my plan is probably to just play with the stock configuration for a month or two just to get used to working with a modern android version (I'm coming from a Droid 2 with large areas of pixel smear...so anything will be an improvement).
Hopefully, after a couple months if I am feeling like I want to tinker, sunshine will have come down in $$ or there is another working method. If not, I'll pay for it if I feel it's worth what I'll gain at that time. In all honesty, I like knowing I have the power to do whatever I want on my phone, but because I use my phone day in and out for business, I'm not often that adventurous in constant flashing ROMs as I want a very stable experience and don't want to take the time to constantly flash and restore.
I do have a few follow-up questions from some of my reading:
1) My understanding is that S-Off is also equivalent to a bootloader unlock. And that if you S-OFF, there is no need to also unlock the bootloader (it's either done as part of it, or simply not needed since S-Off overrides any boot lock). Is this correct?
2) Is CID unlock necessary to flash custom ROMs? Does doing a CID unlock also have the same benefit of a SIM unlock? Some pages I read indicate that setting to the superCID (11111111) is basically the same as a region unlock and therefore your SIM is also unlocked?
3) Since you can apparently gain temp root with weaksauce, is it possible to use this temproot with xposed framework? Or is S-off still required to apply the xposed framework modules?
thanks!
TraderJack said:
So I've read up on a good bit of what you've all posted - again thanks for that.
My M8 will be here tomorrow and I plan to use it for a few days without any tampering to ensure that I like the phone and that the reception in my home is adequate (problem had on my last upgrade attempt a year ago to a Razr M with Verizon). If all looks good, I will attempt the firewater method this weekend. If unsuccessful, I think my plan is probably to just play with the stock configuration for a month or two just to get used to working with a modern android version (I'm coming from a Droid 2 with large areas of pixel smear...so anything will be an improvement).
Hopefully, after a couple months if I am feeling like I want to tinker, sunshine will have come down in $$ or there is another working method. If not, I'll pay for it if I feel it's worth what I'll gain at that time. In all honesty, I like knowing I have the power to do whatever I want on my phone, but because I use my phone day in and out for business, I'm not often that adventurous in constant flashing ROMs as I want a very stable experience and don't want to take the time to constantly flash and restore.
I do have a few follow-up questions from some of my reading:
1) My understanding is that S-Off is also equivalent to a bootloader unlock. And that if you S-OFF, there is no need to also unlock the bootloader (it's either done as part of it, or simply not needed since S-Off overrides any boot lock). Is this correct?
2) Is CID unlock necessary to flash custom ROMs? Does doing a CID unlock also have the same benefit of a SIM unlock? Some pages I read indicate that setting to the superCID (11111111) is basically the same as a region unlock and therefore your SIM is also unlocked?
3) Since you can apparently gain temp root with weaksauce, is it possible to use this temproot with xposed framework? Or is S-off still required to apply the xposed framework modules?
thanks!
Click to expand...
Click to collapse
1) s-off is not equivalent to bootloader unlock, they are different things. S-off is needed to unlock bootloader.
2) super cid is only needed if swapping carriers, it allows another rom specific to any carrier to be flashed. If you flash any rom on Verizon it won't work, so you have to use a compatible Verizon rom anyways.
3) maybe, I never use xposed anyway because it breaks some apps I use. My guess is that it would be hit or miss depending on what the module does.
Sent from my HTC6525LVW using Tapatalk
TraderJack said:
So I've read up on a good bit of what you've all posted - again thanks for that.
My M8 will be here tomorrow and I plan to use it for a few days without any tampering to ensure that I like the phone and that the reception in my home is adequate (problem had on my last upgrade attempt a year ago to a Razr M with Verizon). If all looks good, I will attempt the firewater method this weekend. If unsuccessful, I think my plan is probably to just play with the stock configuration for a month or two just to get used to working with a modern android version (I'm coming from a Droid 2 with large areas of pixel smear...so anything will be an improvement).
Hopefully, after a couple months if I am feeling like I want to tinker, sunshine will have come down in $$ or there is another working method. If not, I'll pay for it if I feel it's worth what I'll gain at that time. In all honesty, I like knowing I have the power to do whatever I want on my phone, but because I use my phone day in and out for business, I'm not often that adventurous in constant flashing ROMs as I want a very stable experience and don't want to take the time to constantly flash and restore.
I do have a few follow-up questions from some of my reading:
1) My understanding is that S-Off is also equivalent to a bootloader unlock. And that if you S-OFF, there is no need to also unlock the bootloader (it's either done as part of it, or simply not needed since S-Off overrides any boot lock). Is this correct?
2) Is CID unlock necessary to flash custom ROMs? Does doing a CID unlock also have the same benefit of a SIM unlock? Some pages I read indicate that setting to the superCID (11111111) is basically the same as a region unlock and therefore your SIM is also unlocked?
3) Since you can apparently gain temp root with weaksauce, is it possible to use this temproot with xposed framework? Or is S-off still required to apply the xposed framework modules?
thanks!
Click to expand...
Click to collapse
1) No, s-off simply allows you to write to the /system partition and do some other stuff like RUU's and etc that i cant think of at the moment but no it is not equivalent to bootloader unlock. Bootloader unlocking allows you to flash recoveries, roms, scripts, kernels, etc. S-OFF allows the more advanced stuff like firmware flashing in fastboot. (at least I think that's what s-off does)
2) Super CID allows you to flash ROM's made for other carriers. So if you set your CID to super CID or another carriers CID then you could flash their ROMS and receive OTA Updates from them. It does not allow Sim unlock and or is not a Sim unlock.
3) I'm quite sure that weak sauce only allows access to /system/xbin but I may be wrong BUT in the case I'm right then no you cannot use xposed without S-OFF because without S-OFF you can't flash a system write enabled kernel to allow it.
Ok... so two more questions:
1) Verizon M8 is already SIM unlocked, correct?
2) I can see that firewater/sunshine do both an S-off and bootloader unlock. However, they don't seem to differentiate between these two things, simply stating they do both. Is there another stand-alone method to unlock the bootloader and if so, do you gain anything having an unlocked boot loader but not s-off? I know you can unlock the bootloader on all the other M8 variants via HTCdev, but they have blocked Verizon.
TraderJack said:
Ok... so two more questions:
1) Verizon M8 is already SIM unlocked, correct?
2) I can see that firewater/sunshine do both an S-off and bootloader unlock. However, they don't seem to differentiate between these two things, simply stating they do both. Is there another stand-alone method to unlock the bootloader and if so, do you gain anything having an unlocked boot loader but not s-off? I know you can unlock the bootloader on all the other M8 variants via HTCdev, but they have blocked Verizon.
Click to expand...
Click to collapse
1) No, you have to manually unlock it.
2) HTCDev is the only way that I've heard about for unlocking the bootloader alone & the only thing different is you wouldn't be able to flash firmware I believe.
S1L3nTShaDoWz said:
1) No, you have to manually unlock it.
Click to expand...
Click to collapse
http://htcsource.com/2014/06/how-to-sim-unlock-the-htc-one-m8-for-free/
"Verizon: the HTC One (M8) from Verizon is SIM unlocked right out of the box."
Also found this on Verizon's Global Ready policy FAQ:
http://www.verizonwireless.com/support/faqs/InternationalServicesandRoaming/faq_global_phone.html
"We do not lock our 4G LTE devices, and no code is needed to program them for use with another carrier."
Some info on this thread people seem to indicate it is already unlocked:
http://forum.xda-developers.com/showthread.php?t=2730159
So are those sources above incorrect? I can't find any guide on how to SIM unlock the M8 on verizon... this is why I'm thinking it was already unlocked?
TraderJack said:
http://htcsource.com/2014/06/how-to-sim-unlock-the-htc-one-m8-for-free/
"Verizon: the HTC One (M8) from Verizon is SIM unlocked right out of the box."
Also found this on Verizon's Global Ready policy FAQ:
http://www.verizonwireless.com/support/faqs/InternationalServicesandRoaming/faq_global_phone.html
"We do not lock our 4G LTE devices, and no code is needed to program them for use with another carrier."
Some info on this thread people seem to indicate it is already unlocked:
http://forum.xda-developers.com/showthread.php?t=2730159
So are those sources above incorrect? I can't find any guide on how to SIM unlock the M8 on verizon... this is why I'm thinking it was already unlocked?
Click to expand...
Click to collapse
It is sim unlocked, you can take it into any carrier and it'll work. The only reason it wouldn't work is if you don't have the correct bands to get LTE or GSM data.
Sent from my HTC6525LVW using Tapatalk
So i got my M8 yesterday and could already tell that reception wise it was much better than my previous upgrade attempt with the RAZR M.
Since there aren't a lot of options for customizable phones anymore with VZW, I've decided to keep it and am happy to report that firewater worked for me to S-OFF!
I had some issues with weaksauce and superSU...the latter not seeming to want to run, but eventually I determined that it wasn't necessary to actually run and update the app to get firewater to work (even though I never got any toast pop-ups from weaksauce after boot).
Firewater ran find and unlocke me after 4 bottle chugs.
I then had some problems loading on CWM. The reason is that on the CWM site the list the M8 down at the very bottom away from all the other HTC devices (including the HTC One - which they don't qualify as the M7 or M8). I accidentally flashed the recovery for the M7 since that is what was listed. After that I couldn't get into any recovery, although the phone still booted. When I realized what happened, I was a little peeved that they so carelessly listed these on their site that I chose not to continue using the stock CWM even though I prefer it's streamlined approach.
I went ahead an installed this version of PhilZ CWM:
http://forum.xda-developers.com/showthread.php?t=2725348
It sounded like you guys were praising this one, and I do prefer CWM. Even though it sounds like TWRP is more popular now, I saw several threads where it seemed like there were issues with TWRP doing funky stuff that CWM users didn't have issues with.
So, after I got that on I removed weaksauce and SuperSU.
What I would like to do now is probably reset to factory defaults and do a nandroid backup. Then, I would like to perma-root.
Some questions on this:
1) Do i need an SD card to nandroid backup? It appeared to work when I started a backup without an SD card...I didn't let it finish, but I'm not sure this method will work. I want to make sure I have a backup that I can use to revert to stock. I do have an sd card coming, but if I can do a successful backup without one I will go ahead.
2) Do I use all the default settings in Philz/CWM for the backup, or do I need to tweak anything in the advanced to ensure that I get *everything* that would be stock on the phone?
3) I saw some method that involved flashing a supersu update to get perma-root? Is this the best method?
Thanks again for all the help.
TraderJack said:
So i got my M8 yesterday and could already tell that reception wise it was much better than my previous upgrade attempt with the RAZR M.
Since there aren't a lot of options for customizable phones anymore with VZW, I've decided to keep it and am happy to report that firewater worked for me to S-OFF!
I had some issues with weaksauce and superSU...the latter not seeming to want to run, but eventually I determined that it wasn't necessary to actually run and update the app to get firewater to work (even though I never got any toast pop-ups from weaksauce after boot).
Firewater ran find and unlocke me after 4 bottle chugs.
I then had some problems loading on CWM. The reason is that on the CWM site the list the M8 down at the very bottom away from all the other HTC devices (including the HTC One - which they don't qualify as the M7 or M8). I accidentally flashed the recovery for the M7 since that is what was listed. After that I couldn't get into any recovery, although the phone still booted. When I realized what happened, I was a little peeved that they so carelessly listed these on their site that I chose not to continue using the stock CWM even though I prefer it's streamlined approach.
I went ahead an installed this version of PhilZ CWM:
http://forum.xda-developers.com/showthread.php?t=2725348
It sounded like you guys were praising this one, and I do prefer CWM. Even though it sounds like TWRP is more popular now, I saw several threads where it seemed like there were issues with TWRP doing funky stuff that CWM users didn't have issues with.
So, after I got that on I removed weaksauce and SuperSU.
What I would like to do now is probably reset to factory defaults and do a nandroid backup. Then, I would like to perma-root.
Some questions on this:
1) Do i need an SD card to nandroid backup? It appeared to work when I started a backup without an SD card...I didn't let it finish, but I'm not sure this method will work. I want to make sure I have a backup that I can use to revert to stock. I do have an sd card coming, but if I can do a successful backup without one I will go ahead.
2) Do I use all the default settings in Philz/CWM for the backup, or do I need to tweak anything in the advanced to ensure that I get *everything* that would be stock on the phone?
3) I saw some method that involved flashing a supersu update to get perma-root? Is this the best method?
Thanks again for all the help.
Click to expand...
Click to collapse
1) You don't need an SD card but I recommend it because if you ever encounter the dreaded "encryption" glitch that some AOSP ROM's have then you'll lose everything on your internal storage. I also recommend you back your Nandroid backups to your computer or some other sort of storage too so that if you ever encounter it or somehow manage to lose it then you can get it back.
2) It doesn't really matter what settings you choose or at least it never has for me but it should backup everything (ROM & apps)
3) Yes, that is the best method for getting perma-root is to flash the SuperSU zip in your recovery. You can find the latest version of the flashable zip at Chainfire's thread over here or the direct download link to the flashable zip here on his official website
Also I'd like to apologize for the invalid information I gave you yesterday on the SIM unlocking, my bad on that. I've had a cold for the past few days and it's been making me lazy lol.
S1L3nTShaDoWz said:
1) You don't need an SD card but I recommend it because if you ever encounter the dreaded "encryption" glitch that some AOSP ROM's have then you'll lose everything on your internal storage. I also recommend you back your Nandroid backups to your computer or some other sort of storage too so that if you ever encounter it or somehow manage to lose it then you can get it back.
2) It doesn't really matter what settings you choose or at least it never has for me but it should backup everything (ROM & apps)
3) Yes, that is the best method for getting perma-root is to flash the SuperSU zip in your recovery. You can find the latest version of the flashable zip at Chainfire's thread over here or the direct download link to the flashable zip here on his official website
Also I'd like to apologize for the invalid information I gave you yesterday on the SIM unlocking, my bad on that. I've had a cold for the past few days and it's been making me lazy lol.
Click to expand...
Click to collapse
1) Ok...but to get my first stock backup so I can proceed with everything else, it's safe to nandroid to internal memory? Where exactly will it place a nandroid backup if I don't have an SD card?
2) I was looking at the Misc Nandroid Settings like "include /preload" "use TWRP mode" etc. No reason to use anything but the defaults?
3) Cool...as soon as I have my nandroid I will go that route.
No worries about the SIM data...you guys have helped accelerate me pretty fast, and I'm thrilled that firewater worked. I'd now just like to get my full backup so I can begin fully migrating to the new phone and having fun
TraderJack said:
1) Ok...but to get my first stock backup so I can proceed with everything else, it's safe to nandroid to internal memory? Where exactly will it place a nandroid backup if I don't have an SD card?
2) I was looking at the Misc Nandroid Settings like "include /preload" "use TWRP mode" etc. No reason to use anything but the defaults?
3) Cool...as soon as I have my nandroid I will go that route.
No worries about the SIM data...you guys have helped accelerate me pretty fast, and I'm thrilled that firewater worked. I'd now just like to get my full backup so I can begin fully migrating to the new phone and having fun
Click to expand...
Click to collapse
Yeah it's safe, it will be stored in a folder called TWRP/Backups/Phone_Id_Here/ in the storage/emulated/0 folder (in root Explorer).
Also you can change them around to what you like, it doesn't matter.
& glad we could help!
I'm having all sorts of troubles trying to find any way to unlock my phone. I know with 4.4, I could TempRoot my phone using Sunshine and then, I could S-Off from there, but now you can't even TempRoot on 5.0. If anybody knows of a way or even knows of a downgrade, that would be awesome.
You need to find one of the guys with a java card. There's a thread about java card holders in the m9 forum. Go check it out and see if there's someone close enough to go visit or mail you phone to.
You don't need a java card
http://forum.xda-developers.com/verizon-htc-one-m8/general/downgrade-s-sunshine-purposes-t3202237
Downgrade, temp root with Kingroot, Sunshine, profit
forrestwllms said:
http://forum.xda-developers.com/verizon-htc-one-m8/general/downgrade-s-sunshine-purposes-t3202237
Downgrade, temp root with Kingroot, Sunshine, profit
Click to expand...
Click to collapse
okay i downgraded, i ran Kingroot a couple times and it said root successful but when i go to start to sunshine app my phone restarts.. any thought?
BAttitude7689 said:
okay i downgraded, i ran Kingroot a couple times and it said root successful but when i go to start to sunshine app my phone restarts.. any thought?
Click to expand...
Click to collapse
Keep trying it, it took me several tries, also I think I may have used the desktop version of kingroot.
BAttitude7689 said:
okay i downgraded, i ran Kingroot a couple times and it said root successful but when i go to start to sunshine app my phone restarts.. any thought?
Click to expand...
Click to collapse
It's a PIA to make root stick for Sunshine with King Root but it works. Search the Sunshine thread, people posted what worked for them.
I, too, can confirm Kingroot worked for me on 5.0.1. It is a pain. Just be persistent until it finally works.
I believe BAttitude7689 was successful with rooting his phone (read in another thread)
So I downgraded to whatever that link had. Kingroot ran one time, unsuccessfully, and now gets stuck at "verify root status." I've tried rebooting, reinstalling the app, everything.
Verify root status.... over and over and over.
Uninstall, reinstall kingroot and try again. I literally had to repeat the process nearly a day and a half to finally get it to the point where Sunshine would complete (and got TWRP to install).
I was lucky that my second M8 was a leftover in-store (not a replacement from service center) came with KitKat and I immediately ran Sunshine. But on a friend's replacement from service, it came with 5.0.1 and I had to do the dance. Dottat was thoughtful enough to give us the stagefright downgrader that enables Kingroot to run at all, but it's not a perfect science.
You also have the option to ship the phone to the sunshine devs & they will happily soff your phone. They have a way with 5.0.1, but its not stable for release
Took me about 3 hours last night with a bit of trial and error since every time my phone rebooted I had to Kingroot all over again but eventually for some reason it wound up working. I didn't RUU or flash TWRP until after Sunshine confirmed that I was s-off. Also, try different versions of Kingroot, I played with a few different ones and different SU apks as well.
Drunkula said:
I, too, can confirm Kingroot worked for me on 5.0.1. It is a pain. Just be persistent until it finally works.
Click to expand...
Click to collapse
Yup same here. It took me a like 6 or 8 tries. I also used Sunshine for the next level s-0ff! I was able to install the custom teamwin recovery with flashify too. Custom roms here I go.
Can confirm it works, I rooted 5.0.1 this way as well, and just to chime in with everyone else, it is a pain in the ass, but plenty worth it.
Did anyone else have the problem where the phone rebooted after a successful root? I need to use sunshine to s-off but phone keeps rebooting after a random amount of time. Somewhere between 5 seconds to a minute
---------- Post added at 03:00 PM ---------- Previous post was at 02:57 PM ----------
Sorry I should've read the whole conversation before posting
A new version of sunshine was just released about one or two hours ago. Here is the newest entry in the changelog: Version 3.2.1
Merged Droid Turbo Support into main release
Added new root for Droid Turbo (no more mofo/kingroot needed)
Added new root for Some HTC (like m8, no more htcdev/kingroot needed)
Removed 626s support for now*
Sunshine now works without kingroot
I had been checking the threads every couple weeks for the last few months waiting for Sunshine to get updated to work with Lollipop. As soon as I saw that an update was available and that someone had used it successfully I ran it and it worked great. It is nice to have a rooted phone again. :good:
Since Lollipop was finally released for Verizon Moto G prepaid. I am wondering if it is now more possible to root and unlock the bootloader without paying anything. Lots of people got the phone black Friday last year and wants to root it since it was a cheap phone to get. So lots of people are hoping for a new method for it. Please reply if there is any new info, methods, or anything. Thx
I'm holding off on upgrading in case I get a way to get root on 444, but the nag screen for updating is getting on my nerves so bad I may take it just to make it stop...
I have some very specific reasons for wanting to keep this phone, if only I could get root, then sunshine it, then get a custom 5.1 rom... Ah the dream
I updated my phone to 5.1 on Tuesday (when it came out) and I was wondering the same thing too. I hope someone can find a way to do it
DaxxTrias said:
I'm holding off on upgrading in case I get a way to get root on 444, but the nag screen for updating is getting on my nerves so bad I may take it just to make it stop...
I have some very specific reasons for wanting to keep this phone, if only I could get root, then sunshine it, then get a custom 5.1 rom... Ah the dream
Click to expand...
Click to collapse
Did you try temp root with Kingoroot? Supposedly it works on 4.4.4 and apparently not on 5.1... once you have temp root then onto Sunshine and once your bootloader is unlocked you can even take the 5.1 OTA or for that matter any ROM
dovw said:
Did you try temp root with Kingoroot? Supposedly it works on 4.4.4 and apparently not on 5.1... once you have temp root then onto Sunshine and once your bootloader is unlocked you can even take the 5.1 OTA or for that matter any ROM
Click to expand...
Click to collapse
Kingroot has varying degree's of success for me, but the one constant for me is that my temp root has never once lasted long enough for sunshine's purposes. The tests simply take too long, and my root is gone before it reaches a conclusive point.
About all its good for in my case is to backup some files, or tweak a few other quick settings that can be done in less then a minute
DaxxTrias said:
Kingroot has varying degree's of success for me, but the one constant for me is that my temp root has never once lasted long enough for sunshine's purposes. The tests simply take too long, and my root is gone before it reaches a conclusive point.
About all its good for in my case is to backup some files, or tweak a few other quick settings that can be done in less then a minute
Click to expand...
Click to collapse
I hear you... so if there is currently no root for 4.4.4 and we don't know of anyone working on a root I am not sure what there is to wait for...
Because if I do upgrade, I can't downgrade. And knowing my luck as soon as I get 5.1 a 444 root will come out. Another issue is I'm worried about storage consumption when it moves from dalvik to art runtime. It's my experience that using 5.1s ART system will increase all file sizes across the board, I'm already strapped for space.
Sent from my XT1028 using Tapatalk
DaxxTrias said:
I'm holding off on upgrading in case I get a way to get root on 444, but the nag screen for updating is getting on my nerves so bad I may take it just to make it stop...
Click to expand...
Click to collapse
Don't make the rookie mistake !!! It's really trivial to block the nagging upgrade screens. You'll have to use adb from your PC and run something like Debloater ( http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 ). Then find a program named com.motorola.ccc.ota on XT1028, and block it.
I am still hoping that one day we'll get full RW root with 4.4.4 (for free ).
Good point, didn't think to try this. Also I'm holding out hope for that chrome for Android exploit that was revealed in Tokyo last week at PacSec. When last I checked no details yet, but no patch by Google yet either.
Sent from my XT1028 using Tapatalk
I am still waiting to see if there is a way to unlock/root Verizon Moto G Lollipop (XT1028). Any luck?
tired of this phone
I'm sorry to say it but I think that it's a lost cause and its a shame its a great phone and it was a learning experience for me. I'll never buy a prepaid phone from Verizon again I'm moving on to the newest moto g. From what I've been hearing MOTOs are going to be phased out eventually by lenovo so I think it's best to upgrade before its too late. Its just my opinion but I think it's a foolish move on their part cause the moto series is one of the best out there for the price I've had Samsung, HTC,and a few other brands that aren't even worth mentioning (zte/kyocera/BlackBerry/I phone) and Motorola is the best value by far the only downside is the locked bootloaders it's a shame no one is working on the xt 1028 it was a great little phone
Kingroot 4.8 works. But only temporary root. and sometimes later everything crashes
System cant be writable, still
I still have my xt1028 and keep hoping people will report root. I've intentionally avoided upgrading it to 5.1 hoping I can get root 1 way or the other
My phone I bought to replace this one (VS880, LG G Vista for Verizon) was able to be rooted, its a crying shame this one still cant be rooted.
I was about to root it after installing busy box (no root) and then running the king-root app a few times after that i was able to root it but only a temp root, however having the temp root i was about to uninstall some of the unnecessary system apps but i would like to have a full root on this phone and a custom ROM i know it is possible because i have been searching the internet for years looking for a way to root it and i have found custom roms and recoverys for it so its possible to root we just need to find how because how and why would custom roms and recoverys be made for this phone if you can't flash then so there has to be something out there that can help.
I'm so sad of hearing this, I just got this phone ( xt1028 ) as a gift two days ago and I was quick to figured out it needs to be rooted because it don't have SD slot so all the verizon crapp can be removed, this news just upset me.
New update??
I upgraded to 5.1 and notice there is an update pending. Anyone know what they are patching? I doubt they would push out another update for this phone unless something is vulnerable.
I guess if obtaining root was possible, someone would have done it by now. I would've liked to install a Marshmallow ROM, but 5.1 works great, so that's something.
Why
I'm always do what ever you said but I didn't find anything I have search
I've made this thread to teach T337A owners how to root their device with SuperSU. Please note that this is a system-less root, meaning it's temporary, but can be re-applied. Rooting only takes about 5-7 minutes and brings numerous tweaks and advantages to your device. Just remember that every time you reboot or shut the device down, you will need to repeat the rooting process. This tutorial was designed for Lollipop 5.1.1, but it should work on KitKat as well.
Before beginning, you will need to download the following file, unzip it on your pc, then transfer it to your device's internal storage/external sd card.
T337AUCU2BOH4 (Lollipop) firmware can be found here
Root Files can be found here
Lets start!
1) Install both the APK files in the file on your device, If prompted, allow installation from unknown sources.
2) Make sure your device is connected to WiFi, then open Kingroot.
3) Once Kingroot is "Done searching for the best root strategy", click the "Try Now" button and wait about 3 minutes for KingRoot to give you a "Root Successfully" message.
4) This is where it gets kinda tricky, immediately after receiving the root success message, go into SuperSU-me, and grant root permissions when prompted.
5) Click on the big blue button in the middle of the frame and wait about 1 minute for the process to complete. DO NOT UPDATE THE SUPERSU BINARY, IT WILL CAUSE YOUR DEVICE TO BOOTLOOP.
6) IMMEDIATELY after the process has completed, go into Settings and make sure KingRoot or Purify is not installed! This is an important step because Kingroot and Kingroot adware tends to install itself in the system partition which can cause problems and frustration.
7 - Recommended) Download a root file explorer (such as ES File Explorer) and search "King" under /data and /system to ensure that the KingRoot app and its bloatware has been wiped from the system. This is to ensure that Kingroot still works properly after a reboot.
8) Enjoy root access!
If this tutorial helped you please be sure to hit the :good: button. If you had any issues or troubles during this process please feel free to let me know down below.
Cheers!
@KingOfTheNet
will flashfire work? bc it wont with kingroot
also, could itit.d be enabled and run these off of a script for example on startup so we don't have to do this after each reboot/shutdown
but i believe you would have to capture kingroots data somehow in the process of rooting
toolhas4degrees said:
@KingOfTheNet
will flashfire work? bc it wont with kingroot
also, could itit.d be enabled and run these off of a script for example on startup so we don't have to do this after each reboot/shutdown
but i believe you would have to capture kingroots data somehow in the process of rooting
Click to expand...
Click to collapse
FlashFire does work on SuperSU, I've tested that for myself. It does not work with KingRoot.
For the second question, I'm not sure. I haven't looked through that file myself and I might look through it later but right now, I would just avoid rebooting the tablet if you wanna keep root without repeating the process over and over again. It's what I do, repeating the process over and over again can get very tedious and annoying.
Cheers!
I assume you're talking about 5.1.1? It won't work with kingroot versions higher than 4.8. Also, flashfire will load, but if you try to flash a zip you're screwed. You can actually use replace kingroot with supersu zip in terminal emulator on any version kingroot. Same deal with su binary, don't update it. Wish I could figure out how I had permanent for with kingroot. I had to go messing with things and lost it. Nothing really special about this method, unless there's a dev out there that can do something with it.
xjimmy said:
I assume you're talking about 5.1.1? It won't work with kingroot versions higher than 4.8. Also, flashfire will load, but if you try to flash a zip you're screwed. You can actually use replace kingroot with supersu zip in terminal emulator on any version kingroot. Same deal with su binary, don't update it. Wish I could figure out how I had permanent for with kingroot. I had to go messing with things and lost it. Nothing really special about this method, unless there's a dev out there that can do something with it.
Click to expand...
Click to collapse
Sorry for the late response. Yes, somethings I forgot to mention in the original post:
1)Updating the SU Binary will put your device in a bootloop
2)Flashing anything with flashfire (based on what I've seen) results in a soft brick
3) I know you can replace kingroot with SuperSU in terminal, but when you reboot, you're unrooted again.
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Cheers!
Hi, @KingOfTheNet, thanks for helping out with this device, i rooted my device on KK nk2 build and now updated to 5.1.1, thanks to you! now i would like to root 5.1.1 (am aware it is a temp. root)
i have superSu Pro, do i need Super Sume for this to work?
KingOfTheNet said:
Sorry for the late response. Yes, somethings I forgot to mention in the original post:
1)Updating the SU Binary will put your device in a bootloop
2)Flashing anything with flashfire (based on what I've seen) results in a soft brick
3) I know you can replace kingroot with SuperSU in terminal, but when you reboot, you're unrooted again.
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Cheers!
Click to expand...
Click to collapse
Somehow I had it permanently rooted with kingroot a while back. I had the 4.9.6 apk on my tab at the time, is all I know. I could've updated from an earlier version, and maybe that was the cause. I've tried so many different versions of kingroot with no luck, but one peculiar occurrence; if I open kingroot, get into the settings and uninstall kingroot without saving a backup of root, then delete all the files in the tablet's main directory, and reinstall kingroot version 4.8.0, it somehow retains a partial permanent root. At least on my T337A running 5.1.1 BOH4 it will, as long as I get a fresh install of 4.8.0, let it root, then hit the optimize button right after. Then wait until it finally tells me that kingroot has been deployed as a system app. After that, when I try to open any root apps, the screen will darken as it does when the root permission tab pops up, but it never pops up. The app just freezes. I can kill it in the task manager screen to just go back to using my tablet. After I restart the tab, sometimes it'll tell me an app has been granted superuser permissions. If I open up terminal emulator, type in the 'su' command and hit enter, the screen will turn dark again like it's going to ask me to allow or deny superuser permission, but it just freezes like that again. I've tried all kinds of stuff with 4.8.0, but I still can't get it to stick. If you don't hit the optimize button in kingroot right after rooting, and just wait for kingroot to install as a system app, the allow/deny prompt comes up without freezing, but the partial permanent root glitch doesn't remain. ugh, tired of messing with it though. lol
Edit: I may be wrong. It might need to be rooted with 4.8.0, optimized, then rebooted right away for the partial root. I'll try to do it again and let you know what I find.
bklyndiaz said:
Hi, @KingOfTheNet, thanks for helping out with this device, i rooted my device on KK nk2 build and now updated to 5.1.1, thanks to you! now i would like to root 5.1.1 (am aware it is a temp. root)
i have superSu Pro, do i need Super Sume for this to work?
Click to expand...
Click to collapse
I'm happy to help out! You'd need king root installed, root the tab with king root, then use SuperSU me to replace the kingroot binaries with the SuperSU ones. It is an automatic process and should only take about 30 seconds or less. Pro version of SUPERSUme is not required, free version should work just fine.
Cheers!
xjimmy said:
Somehow I had it permanently rooted with kingroot a while back. I had the 4.9.6 apk on my tab at the time, is all I know. I could've updated from an earlier version, and maybe that was the cause. I've tried so many different versions of kingroot with no luck, but one peculiar occurrence; if I open kingroot, get into the settings and uninstall kingroot without saving a backup of root, then delete all the files in the tablet's main directory, and reinstall kingroot version 4.8.0, it somehow retains a partial permanent root. At least on my T337A running 5.1.1 BOH4 it will, as long as I get a fresh install of 4.8.0, let it root, then hit the optimize button right after. Then wait until it finally tells me that kingroot has been deployed as a system app. After that, when I try to open any root apps, the screen will darken as it does when the root permission tab pops up, but it never pops up. The app just freezes. I can kill it in the task manager screen to just go back to using my tablet. After I restart the tab, sometimes it'll tell me an app has been granted superuser permissions. If I open up terminal emulator, type in the 'su' command and hit enter, the screen will turn dark again like it's going to ask me to allow or deny superuser permission, but it just freezes like that again. I've tried all kinds of stuff with 4.8.0, but I still can't get it to stick. If you don't hit the optimize button in kingroot right after rooting, and just wait for kingroot to install as a system app, the allow/deny prompt comes up without freezing, but the partial permanent root glitch doesn't remain. ugh, tired of messing with it though. lol
Edit: I may be wrong. It might need to be rooted with 4.8.0, optimized, then rebooted right away for the partial root. I'll try to do it again and let you know what I find.
Click to expand...
Click to collapse
Kingroot does allow your device to retain permanent root after a certain time. However, Kingroot is not as powerful as SuperSU, is very limited in terms of what It can do, and has it's own 'bloatware' titled Purify. I'd honestly stick with SuperSU because it's (probably) the most powerful and efficient way to root your phone. I'd also suggest avoiding having to reboot the tablet at all with temp root because you would have to take 5 minutes to install it again, which was a pain in the butt for me.
As for the kingroot app freezing, that's usually the result of a bad download or a bad root. Plus kingroot is very limited in terms of what you can do on your kingrooted device. SUPERSU is the equivalent of an IOS jailbreak. SUPERSU gives you full control of your device, with no bloatware and limits, unlike kingroot.
Kingroot does sometimes delete the su binaries upon rebooting, which is another reason I don't like it all that much.
Another theory I thought of is that it's not Kingroot that's deleting the binaries, it's actually something that's set to happen when the device boots up. Either the actual Android os or the bootloader searches for and deletes the su binaries to prevent root.
I don't know for sure, I've kinda slowed down work on this device mainly because of a project I've been working on with the Samsung Galaxy S7 AT&T (SM-G930A). I'll look into these things when I get the chance.
Cheers!
I understand the limitations of Kingroot, and certainly supersu by all means is better. In the case of flashfire with supersu in this scenario, it's merely the difference of being able to open and run it just enough to work improperly and brick your device vs. Kingroot not being able to open it at all. I posted in a thread long before this one, how to replace kingroot with supersu, only I use the zip file in terminal emulator. Pretty sure I went over flashfire as well. The terminal emulator method works with new versions of kingroot, unlike supersu me. Are you suggesting that the T337A running 5.1.1 BOH4 can achieve permanent root via kingroot after "a certain amount of time"? Because I'm the only one I've seen on xda who's ever posted that they had permanent root from kingroot, but I didn't know how I did it. After I messed with things, i softbricked and had to flash back to stock, which, no offense, the stock file was available way before you posted it. Anyway, it's not the kingroot app freezing per se, i was talking about after rebooting, and without re-rooting, when trying to use rooted apps, they actually start to engage in the kingroot request superuser permissions pop-up. So, no, it's not a bad download, etc. I believe an older version of kingroot somehow permanently rooted my tab, perhaps with the help of something I was messing with at the time, perhaps not. I've intentionally rebooted my tab an unimaginable amount of times, testing to see if I possibly regained permanent root to no avail, so I know how that works. And it's not about having a hard time deciding on kingroot or supersu for a temproot, it's the interest in permanent root, the possibility off something like safestrap, and/or flashing custom roms, etc. When people say temproot is better or safer, i say boo. How many custom roms include a root toggle in the settings? Anyway I wish I could've gotten hold of a developer while I had permanent root. Maybe I could've done a system dump, or even try replacing the permanent kingroot with supers and drying out that could've stuck. You say you slowed down on this device, do you mean you were pursuing permanent root for it? Are you a developer? I have the AT&T S7 Edge (G935A). What's your project on the 930? Is it something for rooted S7's? I still have my edge running the engboot with the echoRom. Anyway, thanks for your reply.
---------- Post added at 01:01 AM ---------- Previous post was at 12:51 AM ----------
https://forum.xda-developers.com/tab-4/help/t337a-temp-root-bootlp-fix-tar-official-t3473737
*https://forum.xda-developers.com/tab-4/general/permanent-root-t337a-5-1-1-kingroot-t3518334
A couple of threads I started a long time ago that may be of interest to you.
xjimmy said:
I understand the limitations of Kingroot, and certainly supersu by all means is better. In the case of flashfire with supersu in this scenario, it's merely the difference of being able to open and run it just enough to work improperly and brick your device vs. Kingroot not being able to open it at all. I posted in a thread long before this one, how to replace kingroot with supersu, only I use the zip file in terminal emulator. Pretty sure I went over flashfire as well. The terminal emulator method works with new versions of kingroot, unlike supersu me. Are you suggesting that the T337A running 5.1.1 BOH4 can achieve permanent root via kingroot after "a certain amount of time"? Because I'm the only one I've seen on xda who's ever posted that they had permanent root from kingroot, but I didn't know how I did it. After I messed with things, i softbricked and had to flash back to stock, which, no offense, the stock file was available way before you posted it. Anyway, it's not the kingroot app freezing per se, i was talking about after rebooting, and without re-rooting, when trying to use rooted apps, they actually start to engage in the kingroot request superuser permissions pop-up. So, no, it's not a bad download, etc. I believe an older version of kingroot somehow permanently rooted my tab, perhaps with the help of something I was messing with at the time, perhaps not. I've intentionally rebooted my tab an unimaginable amount of times, testing to see if I possibly regained permanent root to no avail, so I know how that works. And it's not about having a hard time deciding on kingroot or supersu for a temproot, it's the interest in permanent root, the possibility off something like safestrap, and/or flashing custom roms, etc. When people say temproot is better or safer, i say boo. How many custom roms include a root toggle in the settings? Anyway I wish I could've gotten hold of a developer while I had permanent root. Maybe I could've done a system dump, or even try replacing the permanent kingroot with supers and drying out that could've stuck. You say you slowed down on this device, do you mean you were pursuing permanent root for it? Are you a developer? I have the AT&T S7 Edge (G935A). What's your project on the 930? Is it something for rooted S7's? I still have my edge running the engboot with the echoRom. Anyway, thanks for your reply.
---------- Post added at 01:01 AM ---------- Previous post was at 12:51 AM ----------
https://forum.xda-developers.com/tab-4/help/t337a-temp-root-bootlp-fix-tar-official-t3473737
*https://forum.xda-developers.com/tab-4/general/permanent-root-t337a-5-1-1-kingroot-t3518334
A couple of threads I started a long time ago that may be of interest to you.
Click to expand...
Click to collapse
No offence taken on the firmware post, I was simply trying to spread the fact that the firmware for the device does exist but is very hard to find and is often posted on shady websites for money, unless you're looking in the right places. It only took me 5 minutes on Google to find one of those sites.
You asked if I was saying that the Tab 4 BOH4 firmware allows you to retain permanent root after some time, and yes, that's exactly what I was saying. I rooted my tablet with Kingroot 4.8.0 a while back and after about 4 - 5 reboots (I counted how many times I rebooted it, but the numbers could vary), It retained root. All I do today is avoid rebooting the tablet at all costs. I prefer SuperSU because, like we've said, there are almost no limitations of what you can do in terms of being rooted. I'm trying to find out how I can make root permanent on the tab with SuperSU by using the eng-boot method used to root all Qualcomm variants of the Galaxy S7, but that may take a while. Since my S7 has the eng-boot root method, I can reboot it all I want and it stays rooted with SuperSU. But at this point, It's just an Idea. I mainly need to find out whether or not the bootloader or the os is wiping the binaries on boot. Some older and newer versions of kingroot can retain root after reboot, but I have yet to find a version of the app that can do so.
Actually, some versions of Cyanogenmod and other custom roms had root pre-installed (not like SuperSU, but close enough), and like CM specifically, there was a section in the settings app for this pre-baked root. Even if I still used CM today, I still would've flashed SuperSU. But on a small number of devices, temp root really is better. However, most of those devices that would be on that list have very little to no development on them. Thus, they are not yet (and may never be) supported for permanent root.
I am partially on the road to becoming a developer, but I don't know how far that's gonna go (my prediction is not that far at all). I was doing research on how I could make an eng-boot for the Tab 4, but I became interested in my Galaxy S7 (AT&T). By that, I mean I wanted to make my own custom version of the stock Marshmallow rom ("Custom but stock OS"). To shorten it up, I wanted to create a .zip flashable "super package" which included SuperSU v2.79, Viper4Android, Overclock tools, and other stuff. I've kinda been on and off in terms of motivation to make this idea a reality, primarily because most of the things I wanted to include in this "package", can easily be installed by you in like 3 minutes, or maybe less. The original motive behind the idea was to lessen the work for power users who wanted to free their device "from the shackles". I've been on and off on work between both devices, but It's hard for me to continue the work without proper motivation. These projects are merely just an Idea at this point, but some drafts and copies do exist on my computer.
Creating a custom Android rom straight from my own head is basically an impossible task for me, considering most of the devices I work with have locked bootloaders. I am still learning Java and other Android programming languages in some of my free time but, again, the motivation to continue is something I struggle to find.
Cheers!
Upgrading OS and rooting
I am currently running my t337a on 4.4.2 with build NK2. I was able to root with towel root awhile ago. I want to upgrade my os to 5.1.1 and root after but would like to make sure I go about it the right way.
Any help would be greatly appreciated. Thanks in advance!
loc626 said:
I am currently running my t337a on 4.4.2 with build NK2. I was able to root with towel root awhile ago. I want to upgrade my os to 5.1.1 and root after but would like to make sure I go about it the right way.
Any help would be greatly appreciated. Thanks in advance!
Click to expand...
Click to collapse
You can root on the latest Lollipop firmware, but it's systemless supersu/temporary, meaning it will go away if you shutdown or reboot the device (you can re-root it, of course, but It can be annoying). The option to upgrade is up to you, and once you do upgrade, you can't downgrade (Locked bootloader & different bootloader versions. Lollipop has the new bootloader.) If you are going to upgrade, you can flash the Lollipop firmware via Odin or upgrade via OTA. If upgrading, I recommend taking it over the air, mainly because I'm still working up Odin packages for them. The Odin packages that I do have available are the BOH4 (the previous and the initial Lollipop update) ones, so if you upgrade OTA, it'll take away one step in the upgrade process, making your life a tad bit easier. Reply back if you need further help or have any more questions.
Cheers!
KingOfTheNet said:
You can root on the latest Lollipop firmware, but it's systemless supersu/temporary, meaning it will go away if you shutdown or reboot the device (you can re-root it, of course, but It can be annoying). The option to upgrade is up to you, and once you do upgrade, you can't downgrade (Locked bootloader & different bootloader versions. Lollipop has the new bootloader.) If you are going to upgrade, you can flash the Lollipop firmware via Odin or upgrade via OTA. If upgrading, I recommend taking it over the air, mainly because I'm still working up Odin packages for them. The Odin packages that I do have available are the BOH4 (the previous and the initial Lollipop update) ones, so if you upgrade OTA, it'll take away one step in the upgrade process, making your life a tad bit easier. Reply back if you need further help or have any more questions.
Cheers!
Click to expand...
Click to collapse
I'm highly considering an upgrade for the feel and hopefully a better performance. Also, a few apps I have need updates but only compatible on Android 5 and up. I have the OTA ready to go. Would I need to unroot before upgrading the OS?
loc626 said:
I'm highly considering an upgrade for the feel and hopefully a better performance. Also, a few apps I have need updates but only compatible on Android 5 and up. I have the OTA ready to go. Would I need to unroot before upgrading the OS?
Click to expand...
Click to collapse
It would be best to unroot before installing to avoid any issues during the installation. Other then that, you're in the clear! Just remember, you cannot downgrade after the install!
Cheers!
KingOfTheNet said:
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Click to expand...
Click to collapse
I have always been under the assumption that the boot.img for the locked BL on the s7 was literally an engineering kernel from Samsung, and not something Chainfire created. The reason Im saying this is because if Chainfire created a boot image that can get around a locked bootloader, then logic should state that he cracked Sprint/ATT's signature for the BL. So my way of thinking is the success of even one locked boot loader ... it should apply across the board for all, correct? Or am I waaaaay off? lol
leeboski44 said:
I have always been under the assumption that the boot.img for the locked BL on the s7 was literally an engineering kernel from Samsung, and not something Chainfire created. The reason Im saying this is because if Chainfire created a boot image that can get around a locked bootloader, then logic should state that he cracked Sprint/ATT's signature for the BL. So my way of thinking is the success of even one locked boot loader ... it should apply across the board for all, correct? Or am I waaaaay off? lol
Click to expand...
Click to collapse
(1st question) Actually yeah, lol. It was an engineering kernel, he didn't make it . I'm assuming that was used during the development of the phone so Samsung and AT&T could construct the OS without running into any issues with the phones locked bootloader. At the time, I thought that Chainfire thought of some "mad science" to altar the boot.img so that it wont check the signatures of any of the files on boot.
Now I'm thinking:
1) He found a way to obtain all the phones signatures so that way he knows what signature the desired files (like a build of TWRP, or instance) would have to have so it can flash and boot properly.
--OR--
2) He somehow obtained or reproduced the engineering kernel that, like I said, was most likely used during software development for the phone (constructing the OS and the rest of the software).
I've done a little research on what engineering kernels actually do and why they are so useful now (to most people, the name is enough, lol). Apparently, they completely skip some of the signature checks on boot, primarily for /SYSTEM (The OS), which is why we were able to achieve permanent root the Qualcomm Galaxy S7 & S7 edge models. I do not think they skip signature checks for /RECOVERY or /BOOT, but we know that if we either reproduce or obtain the engineering kernel for this tablet, we can achieve permanent root the exact same way. I could be wrong, as I do not know for certain the Ins and outs of engineering kernels and how to get them, but It is very possible.
(2nd question) Now, I do not have much knowledge of bootloaders and signature checks, but I would go to the best assumption that since Sprint & AT&T, for example, are 2 completely different companies and are not affiliated (as of writing this), their bootloaders and updates would not have the same signatures. If they did, then Sprint would have to go to AT&T to sign their updates and such, and AT&T would have to do the same thing for Sprint. It just wouldn't really make sense. Lets think of it this way, If Target wants to sell a product in their stores that's already sold at Walmart, then should Target have to go to Walmart to get that approved? Or if Walmart wanted to sell something that's already sold at Target, then should Walmart have to go to Target for approval? Absolutely not, that wouldn't make any sense. Once again, I could be wrong, but it would make the most sense.
Please, anyone, correct me if I'm wrong.
Cheers!
KingOfTheNet said:
(1st question) Actually yeah, lol. It was an engineering kernel, he didn't make it . I'm assuming that was used during the development of the phone so Samsung and AT&T could construct the OS without running into any issues with the phones locked bootloader. At the time, I thought that Chainfire thought of some "mad science" to altar the boot.img so that it wont check the signatures of any of the files on boot.
Now I'm thinking:
1) He found a way to obtain all the phones signatures so that way he knows what signature the desired files (like a build of TWRP, or instance) would have to have so it can flash and boot properly.
--OR--
2) He somehow obtained or reproduced the engineering kernel that, like I said, was most likely used during software development for the phone (constructing the OS and the rest of the software).
I've done a little research on what engineering kernels actually do and why they are so useful now (to most people, the name is enough, lol). Apparently, they completely skip some of the signature checks on boot, primarily for /SYSTEM (The OS), which is why we were able to achieve permanent root the Qualcomm Galaxy S7 & S7 edge models. I do not think they skip signature checks for /RECOVERY or /BOOT, but we know that if we either reproduce or obtain the engineering kernel for this tablet, we can achieve permanent root the exact same way. I could be wrong, as I do not know for certain the Ins and outs of engineering kernels and how to get them, but It is very possible.
(2nd question) Now, I do not have much knowledge of bootloaders and signature checks, but I would go to the best assumption that since Sprint & AT&T, for example, are 2 completely different companies and are not affiliated (as of writing this), their bootloaders and updates would not have the same signatures. If they did, then Sprint would have to go to AT&T to sign their updates and such, and AT&T would have to do the same thing for Sprint. It just wouldn't really make sense. Lets think of it this way, If Target wants to sell a product in their stores that's already sold at Walmart, then should Target have to go to Walmart to get that approved? Or if Walmart wanted to sell something that's already sold at Target, then should Walmart have to go to Target for approval? Absolutely not, that wouldn't make any sense. Once again, I could be wrong, but it would make the most sense.
Please, anyone, correct me if I'm wrong.
Cheers!
Click to expand...
Click to collapse
No that makes perfect sense and thanks for clearing it up.
The whole thing about the signature being the means by which the bootloader is locked is important. Atleast to me it is, so thank you for clearing that up. :good: And so, it makes sense that the System partitions Signature check being skipped IS what allows access to root. But where my opinion differs on this is the Boot and Recovery implementation of the Signatures. I believe that it IS the carriers implementation that does not allow the Recovery and Boot partitions to be modified. If it were Samsungs then how is Samsung going to incorporate a Universal bootloader that knows how to load all carriers data, policy, etc?
And possibly this is what you were saying above and I am misreading it...
***EDIT*** I see you said that the signatures would NOT be the same between carriers, so I am in line with your theory there as well.
leeboski44 said:
No that makes perfect sense and thanks for clearing it up.
The whole thing about the signature being the means by which the bootloader is locked is important. Atleast to me it is, so thank you for clearing that up. :good: And so, it makes sense that the System partitions Signature check being skipped IS what allows access to root. But where my opinion differs on this is the Boot and Recovery implementation of the Signatures. I believe that it IS the carriers implementation that does not allow the Recovery and Boot partitions to be modified. If it were Samsungs then how is Samsung going to incorporate a Universal bootloader that knows how to load all carriers data, policy, etc?
And possibly this is what you were saying above and I am misreading it...
***EDIT*** I see you said that the signatures would NOT be the same between carriers, so I am in line with your theory there as well.
Click to expand...
Click to collapse
I'm glad I could be of help, however I don't see where I stated that the signature implementations on the BOOT and RECOVERY partitions was Samsung's idea not the carriers, if you could point that out for me that would be great.:good:
The engineering kernels skip SOME signature checks, both when flashing and booting into partitions, but I do not know exactly which ones they skip. We know it skips some of the signatures for /SYSTEM, but it does not do the same for the 2 other main ones, those being /BOOT & /RECOVERY. We know because "one of our own" attempted to flash their own build of TWRP recovery to the device (SM-G930A to be specific) only to get a signature check fail when booting the phone, which of course means that the phone has a locked bootloader and that the signatures for the /RECOVERY partition are still checked, but I do not know for certain about /BOOT. If I had to assume I'd say that /BOOT isn't checked, given the fact that if your phone is rooted then you would have had to flash the engineering kernel, which, like I said, skips some signature checks.
I hope I've cleared most things up for you.
Cheers!
KingOfTheNet said:
I've made this thread to teach T337A owners how to root their device with SuperSU. Please note that this is a system-less root, meaning it's temporary, but can be re-applied. Rooting only takes about 5-7 minutes and brings numerous tweaks and advantages to your device. Just remember that every time you reboot or shut the device down, you will need to repeat the rooting process. This tutorial was designed for Lollipop 5.1.1, but it should work on KitKat as well.
Before beginning, you will need to download the following file, unzip it on your pc, then transfer it to your device's internal storage/external sd card.
Root File: https://mega.nz/#!74Jl0ZqY!knlHuexbYGFkk1f4wHxq16u3L38EtfR9scQ0H7hISTA
Lets start!
1) Install both the APK files in the file on your device, If prompted, allow installation from unknown sources.
2) Make sure your device is connected to WiFi, then open Kingroot.
3) Once Kingroot is "Done searching for the best root strategy", click the "Try Now" button and wait about 3 minutes for KingRoot to give you a "Root Successfully" message.
4) This is where it gets kinda tricky, immediately after receiving the root success message, go into SuperSU-me, and grant root permissions when prompted.
5) Click on the big blue button in the middle of the frame and wait about 1 minute for the process to complete. DO NOT UPDATE THE SUPERSU BINARY, IT WILL BOOTLOOP.
6) IMMEDIATELY after the process has completed, go into Settings and make sure KingRoot or Purify is not installed! This is an important step because Kingroot and Kingroot adware tends to install itself in the system partition which can cause problems and frustration.
7 - Recommended) Download a root file explorer and search "King" under /data and /system to ensure that the KingRoot app and its bloatware has been wiped from the system.
8) Enjoy root access!
If this tutorial helped you please be sure to hit the :good: button. If you had any issues or troubles during this process please feel free to let me know down below.
Need T337A firmware? Check out my thread here: https://forum.xda-developers.com/tab-4/general/download-sm-t337a-lollipop-firmware-t3536509
Cheers!
Click to expand...
Click to collapse
The firmware you provided saved my sm-t337A tablet from being soft bricked. Although I was able to gain temp root from this method, king root tried to disable the SELinux on my device and after trying to temp root again caused the app to implant itself as bloatware into the /systems folder and was non functional when using the app. Do you happen to know of a custom recovery (TWRP or CWM) which would work for this device?
Just goot this device rooted! Just gonna test the script a few times so there isent any bugs and i will upload it!
EDIT: Systemless Root methods like Magisk resets after root(I Think SuperSu works if u tweak dm-verity in the kernel). But using system-root both breaks saftynet and is boring
So im gonna try to edit the boot img to work with magisk or SuperSU even if the bootloader is locked.
If none of theese things works there is a way to Re-root after each reboot but its ofc much easyer just to edit the boot.img or unlock the BL
EDIT 2: I will also try to reverse engineer the bootloader to try to find a weak point where we can unlock it, for easyer rooting and creating custom roms
EDIT 3: Also forgot to mention xposed works because you dont "need" root. If anyone want xposed just reply in the thread and il upload the script "as is" even though it resets after each reboot, but root works perfect have tested multiple apps.
And as i said before, before i release the root method publicly i want to check if its the BL who "resets" the kernel like on some HTC devices or if its a simple dm-verity problem , if it is the dm-verity thing its easy to fix.
More info:
Flashing kernel,system,recovery works because the only partitions that are protected are the BL and FRP partions but not for long
So far:
Magisk: Works
Bootloader: Locked
Saftynet: Passes
Proof:
https://i.imgur.com/8uABTSl.jpg
Download:
Code:
Comming in an hour! Just gotta check the updatescript for errors before posting :)
j wait for your script to root my Z500 m thanks to you.
Wow, finally there's a method to root. I own the device since august and I really want to get it rooted due to all bloatware I want to uninstall and to install 3rd party apps.:good:
super thanks to you me too and thanks to you I could root the tablet with all s is unnecessary thank you for your work:good::good::good:
Cant wait
Wow.... time is ticking to bring root to the P027
I can't wait for an update on this.
There must be another way to get a rooted ASUS P027. I tried much but don't have any success. I think that there is a way to push some files manually to /data/local/tmp. Setting right permissions using adb. Finally executing a root-shell-script from one of many should do the rest. Problem is not to get the files inside the system, you have to do it again after each reboot.
I'm a bit nervous to modify bootloaders and flash them on the go with no oem support. If some support for this device comes available from ASUS it should be a lot easyer to do.
I cant upload photo's till i'm no longer seem like a robot. I also got some kind of root on my P027. only for a moment. After reboot it is gone.
I can't wait for that!
Will it come out soon..... so excited ^_^
BigThanh said:
Will it come out soon..... so excited ^_^
Click to expand...
Click to collapse
here too...the hour is over
That would be great
hey, very good news!! I am waiting a long time for this. It would also be nice, if you can give us your xposed script. Thnkas!!
Is p207 the model number? I'm only finding it listed as Z500M.
joshnat said:
Is p207 the model number? I'm only finding it listed as Z500M.
Click to expand...
Click to collapse
Yes
Ok guy's where do we stand on root as of 5pm Wednesday 10.04.2017 ??
I bought the ASUS Zenpad 3S 10 [P027] off Amazon on Saturday on a flash sale for $265, knowing it didn't have root, and that's a shame because it's a beautiful & buttery smooth tablet.
Today, as I was pondering boxing it up for a return, I figured I'd look for myself once more for the hell-of-it, AND BOOM! I found this thread!
So where are we guys? I'll test it for ya or whatever! So friggin' pumped ROOT has been established! Dare I say -Vanilla Oreo ROM with onscreen softkeys??? YEAH!
Really looking forward to this! I don't mind getting my hands dirty, but just waiting for the script I'm very happy to have stumbled upon this thread, can't wait to have root on this tablet!!
Fortunately we will get to see the script. I own the P027 since auust 17. A very good hardware. But without root its only worth half. So, me too is awaiting the script but so far I guess we still have to wait. Til now, no root app works (iRoot, Kingo, e.g.) Very sad because I think that once we rooted it and get rid of all the OEM bloatware, this tab may rocks a lot more.
Prinz069 said:
Fortunately we will get to see the script. I own the P027 since auust 17. A very good hardware. But without root its only worth half. So, me too is awaiting the script but so far I guess we still have to wait. Til now, no root app works (iRoot, Kingo, e.g.) Very sad because I think that once we rooted it and get rid of all the OEM bloatware, this tab may rocks a lot more.
Click to expand...
Click to collapse
to remove bloatware, i followed this guide. I can confirm ist works.
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Can you go ahead and upload the script for those of us brave enough to try it? Thank you for all your hard work!
I got root and xposed. But I don't have a way to get it in that device
At my next post will I upload a photo or link of my own (semi) rooted P027. The Magic of rooting a device which is unsupported is far away from easy as flashing chainfire's zips or something possible using Odin or what. Most likely if there was a custom recovery for the P027 root would be easy because of all possibilities you have.
I've tried a lot of other ways to get in to try modify something in that locked system. It is hard to get there without losing patients! I also lose social networks I belong to. Even if days counts 48 hour instead of 24, root wasn't there with the success I had hope to. Sometimes only after manually redirecting some files with adb and manually setting right permissions to every file. It becomes possible to get accessing "su" in terminal app. Only sometimes, after each modifying something, you're device needs to reboot for applying that modification. At that point you lose everything before you can use it.
If someone can post latest boot.img I will try to patch it with Magisk. If that is possible it will get easier to activate systemless xposed. A few weeks ago on note 8 launch day... It took at least 1 hell of a day before root came available on xda. Also twrp and custom roms are available.
Hope soon to make it happening for real.
hi I would buy this tablet but wanted to understand root situation. can you run the root on this device? you can install Rom?
toineh said:
At my next post will I upload a photo or link of my own (semi) rooted P027. The Magic of rooting a device which is unsupported is far away from easy as flashing chainfire's zips or something possible using Odin or what. Most likely if there was a custom recovery for the P027 root would be easy because of all possibilities you have.
I've tried a lot of other ways to get in to try modify something in that locked system. It is hard to get there without losing patients! I also lose social networks I belong to. Even if days counts 48 hour instead of 24, root wasn't there with the success I had hope to. Sometimes only after manually redirecting some files with adb and manually setting right permissions to every file. It becomes possible to get accessing "su" in terminal app. Only sometimes, after each modifying something, you're device needs to reboot for applying that modification. At that point you lose everything before you can use it.
If someone can post latest boot.img I will try to patch it with Magisk. If that is possible it will get easier to activate systemless xposed. A few weeks ago on note 8 launch day... It took at least 1 hell of a day before root came available on xda. Also twrp and custom roms are available.
Hope soon to make it happening for real.
Click to expand...
Click to collapse
Here is the boot.img from WW_V14.0210.1709.27: https://mega.nz/#!4bQExBTB!5fyivXxvP4aYAxCDjsYRJ1X7o1wMXYGBLf1TO0ns-z4
I downloaded the WW_V14.0210.1709.27 firmware from ASUS Support then unzip the package to get this file.
Hope it will be helpful to you. I am really looking forward to root this device!
Thank you for your hard work!