Related
hey everyone. i dont come here much but this is kind of a general question. about how many encrypted and or locked bootloaders have been cracked and unlocked in the past? i guess im asking what are the chances that us a500 users will see recovery and roms? i know its up to whoever will figure it out in the end. but im just asking based on past devices. can it be done? has it been done before?
also as a side note. this is just my opinion. i can understand locking the bootloader on a phone so people dont abuse there unlimited data and such. but on a wifi only tablet? its like buying a laptop with a bios password set by the manufacture and the admin account locked out. it just doesn't make any sense to me. they should not be allowed to do this. thoughts?
(please dont take this as a rant. ive been driving myself crazy the past few days and watching the dev forum 24/7)
I don't know how likely it is to happen, but I agree with you it's a ****ty thing to do. It'd be fair in my eyes if we have to register the device, put in our serial number, then request an unlock code that invalidates the warranty to unlock the bootloader. That seems reasonable to me, but just straight up locking me out of my device is ****.
I'm hoping this isn't a trend we're going to have to start accepting. I'd rather the openness of the PC slip into tablets and phones, not the other way around.
Well hopefully that doesn't limit us. They (the community) were able to get around the droid x/2 bootloader to install custom roms, at least in some form. I am hoping this device catches on amongst enthusiasts, together, and by that I mean everyone but me, can work hard on modding this tab...jk.
Thanks for the feedback I'm really glad to know I'm not the only one who feels this way
Unfortunately the same reason Apple products are so successful is that people are very "accepting" , The manufacturers dont count on people hacking there products , its a relatively small amount of people who (even) root Android phones , sure they get the press , but how many "moms and pops" own an Android phone unrooted? The majority of owners dont mess with it , they just buy apps and do what the company tells them!
Look how many people in here whine about updates , obviously if they were rooting there phones the updates wouldnt be a big deal!
While I wait for the arrival of my MXP I have some questions for the community so that I can hit the ground running. First thing, I'd like to unlock my boot loader but I was just curious if there is a way to re-lock it afterwards just in case I need to send in for repairs or something along those lines? Also wondering about VOLTE support. I see some roms that state they have it working but is this a stock feature or do I need to use a custom ROM to get VOLTE to function? Also is there any known method of rooting without unlocking the boot loader just in case re-locking it is not possible? Thanks for the help everyone.
I am coming from a g920a. That phone is torture for someone like me who likes stock Android and rooted devices. Probably the worst phone I have ever had. Can't wait to get my hands on my MXP and leaves this piece of junk behind!
I'm on Verizon and I can confirm it supports advanced calling, which is VoLTE as far as I know but it might require turning it on at the provider level.
Sent from my XT1575 using Tapatalk
I haven't messed with VoLTE yet so I can't answer those questions, but as for your others: The bootloader can be relocked, but the unlock method involves submitting an unlock request code to motorola, and they immediately email you an unlock key, along with a warning about voiding your warranty, so even relocking it does not unvoid your warranty. HOWEVER, it only voids your warranty for software issues. If it's a hardware problem unrelated to the bootloader being unlocked, they'll still handle it, and accidental drops and things are still covered if you buy an accidental damage warrenty. Also, as far as I know there is still no way to root without unlocking the bootloader.
10 characters
squallz506 said:
Volte is only available on stock roms.
Click to expand...
Click to collapse
I thought this had been fixed on AICP based ROMS?
Sent from my XT1575 using Tapatalk
countryfolk07 said:
I thought this had been fixed on AICP based ROMS?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Whoops, yeah I guess they fixed it down the line. Sorry, I've been enjoying stock+xposed too much to follow custom development.
Edit: also root without bootloader unlock will likely never happen. We have a root method already, so there's no incentive to find another method.
The answer you seek was right in the first page of this forum....
http://forum.xda-developers.com/moto-x-style/general/moto-x-style-how-to-unlock-bootloader-t3192140
That being said, I would consider waiting until after Marshmallow drops before you unlock your bootloader so as not to interfere with any OTA's. Conventional wisdom is that it is coming within the next few weeks as the "test drive" has already started and a "soak test" should follow shortly.
yeah i know it can be unlocked I already read that post. I would not have gotten this phone if the boot loader was not un-lockable. That's the whole reason I am moving away from my AT&T Galaxy s6. I was just trying to clarify if re-locking made any difference as far as the warranty is concerned. I appreciate the answers guys. Just trying to determine if I should keep it stock or use a custom ROM out of the box. Sounds like I will go stock for the time being. Now as far as unlocked boot loaders interfering with OTA's? Is this really a thing? And wouldn't somebody just post the OTA image on the forums when its ready anyway?
timde9 said:
yeah i know it can be unlocked I already read that post. I would not have gotten this phone if the boot loader was not un-lockable. That's the whole reason I am moving away from my AT&T Galaxy s6. I was just trying to clarify if re-locking made any difference as far as the warranty is concerned. I appreciate the answers guys. Just trying to determine if I should keep it stock or use a custom ROM out of the box. Sounds like I will go stock for the time being. Now as far as unlocked boot loaders interfering with OTA's? Is this really a thing? And wouldn't somebody just post the OTA image on the forums when its ready anyway?
Click to expand...
Click to collapse
Well as to it being a thing, I certainly can't say for sure. But what reason is there to unlock the bootloader if you're not going to root? And once you do that, you almost certainly will not get OTA's. What am I missing? Is there another reason you are looking to unlock?
The one thing I don't know is if there a some type of a "tamper flag" that would require something like triangle away.
You don't think you could just do a fastboot oem lock?
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
timde9 said:
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
Click to expand...
Click to collapse
I'd still recommend waiting at least a couple of weeks to see if Marshmallow shows up!
I'm coming to the MXPE from a OnePlus One which I have to say was one of the funnest phones I've ever owned. I wasiunlocked, rooted and flashing CM12.1 nightlies about twice a week.
I thought I would miss it, but so far so good on the MXPE without rooting. We'll have to see what happens after MM drops. I'd like to get it rooted, but I haven't done nearly the amount of modding you've done.
Good luck with your phone. I can honestly tell you it's a really nice device!
While its tempting to wait for marshmallow to show I cannot live without root any longer. I have already been without it for months because of this damn s6. I'm sure someone will upload the OTA as soon as it's available so I'll just flash it when the time comes.
timde9 said:
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
Click to expand...
Click to collapse
Well if you're an xposed user you should root immediately with no concern about the 6.0 OTA, since xposed doesn't work on 6.0. I'm not moving to 6.0, myself, until xposed is released for it. I use xposed modules everyday and am not giving it up, not even for doze mode.
That's kinda how I am feeling as well. I can achieve similar results to doze with the xposed app amplify with enough tweaking so its not a big deal.
Hi Friends,
Hope you're all having a great new year. So last time I was lurking the S7E forums, we had a leaked Engineering Bootloader that was used to acquire root on all US Snapdragon models, albeit, with a lot performance issues and etc.
I came here to glance as well as all other variant forums for the SD model and now we have Root for every model, with even ROMs being baked like the Echo ROM for Verizon, Sprint, AT&T models, usually the toughest to achieve these things on. I'm trying to read through the forums, but I fear I'm missing the details, that will help me pull the trigger for getting the device or not.
Can one of you very experienced, knowledgeable, and kind members educate me on the latest?
1. Do we have unlocked Bootloader and Root for all US carrier S7Es? How is it done? I use people using Flashfire. So no TWRP?
2. Does this process still trip Knox and render Samsung Pay to never be used again on the device?
3. If I bought the Verizon variant, for example, can I root, unlock Bootloader, and etc, and then return to stock, to return to the store in case I don't like the phone?
4. Xposed Framework working for all models?
Much appreciate your responses, any and all of them in advance! Thanks!
ProFragger said:
Hi Friends,
Hope you're all having a great new year. So last time I was lurking the S7E forums, we had a leaked Engineering Bootloader that was used to acquire root on all US Snapdragon models, albeit, with a lot performance issues and etc.
I came here to glance as well as all other variant forums for the SD model and now we have Root for every model, with even ROMs being baked like the Echo ROM for Verizon, Sprint, AT&T models, usually the toughest to achieve these things on. I'm trying to read through the forums, but I fear I'm missing the details, that will help me pull the trigger for getting the device or not.
Can one of you very experienced, knowledgeable, and kind members educate me on the latest?
1. Do we have unlocked Bootloader and Root for all US carrier S7Es? How is it done? I use people using Flashfire. So no TWRP?
2. Does this process still trip Knox and render Samsung Pay to never be used again on the device?
3. If I bought the Verizon variant, for example, can I root, unlock Bootloader, and etc, and then return to stock, to return to the store in case I don't like the phone?
4. Xposed Framework working for all models?
Much appreciate your responses, any and all of them in advance! Thanks!
Click to expand...
Click to collapse
Absolutely nothing has changed on root (only possible due to ENG kernel) and bootloader unlock (which is not yet possible).
1. No
2. No
3. No
4. No idea about all models. For the t-mobile one, please check: https://forum.xda-developers.com/tmobile-s7-edge/how-to/guide-installing-xposed-framework-t3414718
You can use the search feature in xda for finding out
CravingMender9 said:
Absolutely nothing has changed on root (only possible due to ENG kernel) and bootloader unlock (which is not yet possible).
1. No
2. No
3. No
4. No idea about all models. For the t-mobile one, please check: https://forum.xda-developers.com/tmobile-s7-edge/how-to/guide-installing-xposed-framework-t3414718
You can use the search feature in xda for finding out
Click to expand...
Click to collapse
Hey bud, thanks for getting the ball rolling on these questions. If you could add some more information, I'd appreciate it :
If we still don't have a way to Root or Unlock bootloader, how are these ROMs (Echo, Tek, and other stock ROMs) available with root? And how are these flashed? Are we somehow bypassing the BL by using FlashFire?
Can you also educate me on the U Firmware and why people install it and is it reverseable?
Lastly, if I got a T-Mobile variant for example, installed these ROMs Tek, Echo, etc, can I return to Stock completely and return to T-Mobile, by any chance for them to take it back? Thank you again!
for the t mobile variant, I was able to flash the U firmware and flash back to stock t mobile. NOTE: I did not flash the U bootloader. I kept the T mobile bootloader just be sure I could flash back to stock t mobile(APK1). I'm sure this method would work with other carriers as well. so what ever variant you have, make sure you stay on that BL and only flash the U firmware CSC and AP. As for the CP(modem) I would flash your carriers latest CP file. That's what worked best for me with the U firmware. Currently I'm using the latest nougat BETA
Thank you very much for your response, bud. One last follow up question: Since all the US variants are rooting based on the ENG Kernel, is there really a benefit of getting one variant over another, for rooting or etc purposes?
P. S. May I ask why you flashed the U Firmware? What are the advantages of it? ?
ProFragger said:
Thank you very much for your response, bud. One last follow up question: Since all the US variants are rooting based on the ENG Kernel, is there really a benefit of getting one variant over another, for rooting or etc purposes?
P. S. May I ask why you flashed the U Firmware? What are the advantages of it?
Click to expand...
Click to collapse
The u firmware basically does not include all of the software that is usually included with the phone. For example.. Tmobile with their software on it, Verizon att etc... Makes the phone a bit snappier especially if you were to root. Even tho I hope for a more stable root still. I am rooted at the moment. Wish they didn't recall the note 7 because the root on that was better
ProFragger said:
Hi Friends,
Hope you're all having a great new year. So last time I was lurking the S7E forums, we had a leaked Engineering Bootloader that was used to acquire root on all US Snapdragon models, albeit, with a lot performance issues and etc.
I came here to glance as well as all other variant forums for the SD model and now we have Root for every model, with even ROMs being baked like the Echo ROM for Verizon, Sprint, AT&T models, usually the toughest to achieve these things on. I'm trying to read through the forums, but I fear I'm missing the details, that will help me pull the trigger for getting the device or not.
Can one of you very experienced, knowledgeable, and kind members educate me on the latest?
1. Do we have unlocked Bootloader and Root for all US carrier S7Es? How is it done? I use people using Flashfire. So no TWRP?
2. Does this process still trip Knox and render Samsung Pay to never be used again on the device?
3. If I bought the Verizon variant, for example, can I root, unlock Bootloader, and etc, and then return to stock, to return to the store in case I don't like the phone?
4. Xposed Framework working for all models?
Much appreciate your responses, any and all of them in advance! Thanks!
Click to expand...
Click to collapse
You're confused. At least, you were.
We do not have an "unlocked Bootloader" and we never did. We had an engineering kernel. That engineering kernel allows certain commands that enabled us to acquire root access. But without that kernel, the system (with the original kernel or boot partition) checks for any changes in the /system partition. If any are found it triggers a bootloop. So basically, if you want root we MUST have the engineering kernel. Unless someone else finds another way that's just the way that it is.
Personally, I unrooted and went back to stock. Root was okay at first but with the lack of development, Samsung Pay and the fact that Android 7+ will probably not be seeing root... well... time to accept the fact that Samsung owns the phone even though we bought it. What else can we do?
nitroevo said:
The u firmware basically does not include all of the software that is usually included with the phone. For example.. Tmobile with their software on it, Verizon att etc... Makes the phone a bit snappier especially if you were to root. Even tho I hope for a more stable root still. I am rooted at the moment. Wish they didn't recall the note 7 because the root on that was better
Click to expand...
Click to collapse
Binary100100 said:
You're confused. At least, you were.
We do not have an "unlocked Bootloader" and we never did. We had an engineering kernel. That engineering kernel allows certain commands that enabled us to acquire root access. But without that kernel, the system (with the original kernel or boot partition) checks for any changes in the /system partition. If any are found it triggers a bootloop. So basically, if you want root we MUST have the engineering kernel. Unless someone else finds another way that's just the way that it is.
Personally, I unrooted and went back to stock. Root was okay at first but with the lack of development, Samsung Pay and the fact that Android 7+ will probably not be seeing root... well... time to accept the fact that Samsung owns the phone even though we bought it. What else can we do?
Click to expand...
Click to collapse
Thanks for your helpful responses fellas. I understand root is not perfect, but for some folks like me, Xposed seems to be worth the trouble. For Samsung Pay, I intend to use the Gear S3 one day ?.
Final question, since all US Snapdragon models are using the engineering kernel to root and etc... Is there a benefit of getting one carrier variant, over another? For example, Verizon is usually the cheapest. Is it wise to get that, with the U Firmware, to use on AT&T? Thanks!
ProFragger said:
For Samsung Pay, I intend to use the Gear S3 one day .
Final question, since all US Snapdragon models are using the engineering kernel to root and etc... Is there a benefit of getting one carrier variant, over another? For example, Verizon is usually the cheapest. Is it wise to get that, with the U Firmware, to use on AT&T? Thanks!
Click to expand...
Click to collapse
Let me know if that works out for you then.
I just purchased the S2 Classic (on T-Mobile) and use Samsung Pay quite a bit. But I can tell you that it does open Samsung Pay on the phone and if you are rooted, Samsung Pay will not work at all. So I'm not sure if it will work at all for you even with the S3.
In regards to your other inquiry, I haven't tried the U firmware. I read something about data issues, no wifi calling (which is pretty important to me), no hotspot (which is also really important to me) but I heard that it is really fast. Not sure how much of that is still a problem but you should probably read up on it before doing anything first. But the rooting method is all the same between carriers I believe. All require the engineering kernel and breaks Samsung Pay along with a couple of other apps.
Just make back ups, have a stock firmware available to flash with ODIN just in case and remember that it's almost impossible to brick this device (because we don't have an unlocked bootloader.)
Binary100100 said:
Let me know if that works out for you then.
I just purchased the S2 Classic (on T-Mobile) and use Samsung Pay quite a bit. But I can tell you that it does open Samsung Pay on the phone and if you are rooted, Samsung Pay will not work at all. So I'm not sure if it will work at all for you even with the S3.
In regards to your other inquiry, I haven't tried the U firmware. I read something about data issues, no wifi calling (which is pretty important to me), no hotspot (which is also really important to me) but I heard that it is really fast. Not sure how much of that is still a problem but you should probably read up on it before doing anything first. But the rooting method is all the same between carriers I believe. All require the engineering kernel and breaks Samsung Pay along with a couple of other apps.
Just make back ups, have a stock firmware available to flash with ODIN just in case and remember that it's almost impossible to brick this device (because we don't have an unlocked bootloader.)
Click to expand...
Click to collapse
Thank you again for a helpful post. So the S3 has a dedicated MST/NFC chip in it, that allows for Samsung Pay to work from the watch, it's done through the Gear app. That's what I have read.
About the rest of it, again, curious to see if there is one US variant, superior to another in terms of Root capabilities or bands and radios available and etc? Can anyone confirm this for me?
Thanks!
ProFragger said:
Thank you again for a helpful post. So the S3 has a dedicated MST/NFC chip in it, that allows for Samsung Pay to work from the watch, it's done through the Gear app. That's what I have read.
Click to expand...
Click to collapse
So does the S2.
When I was setting up the Samsung Pay on my watch it said that it had to download an update.
Then I went through the setup process through my phone which was from the Samsung Pay app.
You go to "Add card" on your watch and it opens Samsung Pay on your phone.
You click "Next" and it displays your Samsung account information.
Then it takes you to a screen that says "Setup complete" telling you that you're ready to use it and at the bottom says "Add card"
You do that all from the Samsung Pay app on your phone which leads me to suspect that if you root your phone, you won't be able to use Samsung Pay on your watch.
People on this thread that you have to set it all up first, remove the Samsung Pay app on the phone but leave it on the watch. If it's all done correctly then it should work. Just make sure you get it all set up first.
Next thing that I'm going to try is using my watch in "Standalone" with my phone out of bluetooth or wifi range. See if that still works.
ProFragger said:
About the rest of it, again, curious to see if there is one US variant, superior to another in terms of Root capabilities or bands and radios available and etc? Can anyone confirm this for me?
Thanks!
Click to expand...
Click to collapse
As far as I know, the U firmware permits use of some other bands that aren't normally used. Not sure which ones though.
Binary100100 said:
So does the S2.
When I was setting up the Samsung Pay on my watch it said that it had to download an update.
Then I went through the setup process through my phone which was from the Samsung Pay app.
You go to "Add card" on your watch and it opens Samsung Pay on your phone.
You click "Next" and it displays your Samsung account information.
Then it takes you to a screen that says "Setup complete" telling you that you're ready to use it and at the bottom says "Add card"
You do that all from the Samsung Pay app on your phone which leads me to suspect that if you root your phone, you won't be able to use Samsung Pay on your watch.
People on this thread that you have to set it all up first, remove the Samsung Pay app on the phone but leave it on the watch. If it's all done correctly then it should work. Just make sure you get it all set up first.
Next thing that I'm going to try is using my watch in "Standalone" with my phone out of bluetooth or wifi range. See if that still works.
As far as I know, the U firmware permits use of some other bands that aren't normally used. Not sure which ones though.
Click to expand...
Click to collapse
Thanks for the correction/education on the S2, bud, much appreciated. I wonder if the rooted phone works with the S3, because Samsung has allowed many other non Samsung phones to know work with the S3? But I could be wrong, I thought it was open like that with the S2 as well, no? Looking forward to your testing, hope there is a breakthrough in there! ?
if you want root and customizability and roms, just don't get this phone. you will be very disappointed with the performance once you root and it gets so much worse with Xposed. not worth it at all, you will have better performance and speed from a 4 year old phone that has an unlocked bootloader and strong development. I mean my Nexus 5 (from 2012) had better performance than my rooted S7. it sounds like you do want roms, and if you want roms then AOSP/Cyanogenmod is the way to go. there will probably never be any AOSP or CM ROM on the QC S7/E so you're better off getting an older galaxy model that does have a great development community and unlocked bootloader. or just get a OnePlus or Nexus or something.
xVermicide said:
if you want root and customizability and roms, just don't get this phone. you will be very disappointed with the performance once you root and it gets so much worse with Xposed. not worth it at all, you will have better performance and speed from a 4 year old phone that has an unlocked bootloader and strong development. I mean my Nexus 5 (from 2012) had better performance than my rooted S7. it sounds like you do want roms, and if you want roms then AOSP/Cyanogenmod is the way to go. there will probably never be any AOSP or CM ROM on the QC S7/E so you're better off getting an older galaxy model that does have a great development community and unlocked bootloader. or just get a OnePlus or Nexus or something.
Click to expand...
Click to collapse
Or a Exynos S7.
Binary100100 said:
Or a Exynos S7.
Click to expand...
Click to collapse
exactly this. except for some reason I thought exynos variants are lacking certain bands/features on American networks. could be wrong.
xVermicide said:
if you want root and customizability and roms, just don't get this phone. you will be very disappointed with the performance once you root and it gets so much worse with Xposed. not worth it at all, you will have better performance and speed from a 4 year old phone that has an unlocked bootloader and strong development. I mean my Nexus 5 (from 2012) had better performance than my rooted S7. it sounds like you do want roms, and if you want roms then AOSP/Cyanogenmod is the way to go. there will probably never be any AOSP or CM ROM on the QC S7/E so you're better off getting an older galaxy model that does have a great development community and unlocked bootloader. or just get a OnePlus or Nexus or something.
Click to expand...
Click to collapse
Binary100100 said:
Or a Exynos S7.
Click to expand...
Click to collapse
xVermicide said:
exactly this. except for some reason I thought exynos variants are lacking certain bands/features on American networks. could be wrong.
Click to expand...
Click to collapse
Very helpful inputs guys, thank you! If I were to be honest with myself, I don't want AOSP/CM/Lineage, especially on a Samsung phone, so unlocked bootloader is not a deal breaker for me. However, I think root is cool for me for doing some SystemUI tweaks, Xposed and etc. Exynos was an option I was exploring, but lack of warranty, no Samsung Pay, and the price are enough to keep me at bay. I think I just need to put my big boy pants on and try to use a phone without rooting it. Something I have yet to do in EVER using an Android phone since about 10 years ago, and I have never ever used or bought an iCrap... I mean... an iPhone !
ProFragger said:
Very helpful inputs guys, thank you! If I were to be honest with myself, I don't want AOSP/CM/Lineage, especially on a Samsung phone, so unlocked bootloader is not a deal breaker for me. However, I think root is cool for me for doing some SystemUI tweaks, Xposed and etc. Exynos was an option I was exploring, but lack of warranty, no Samsung Pay, and the price are enough to keep me at bay. I think I just need to put my big boy pants on and try to use a phone without rooting it. Something I have yet to do in EVER using an Android phone since about 10 years ago, and I have never ever used or bought an iCrap... I mean... an iPhone !
Click to expand...
Click to collapse
Get a One+ 3T good development and really nice phone if you want root. Root is dead on Samsung phones and so are ROMs.
So by reading thru this thread, I assume having a T-mobile S7E (G935T) rooting is pointless and really not available the way I'm used to it coming from a Note 4. That's kind of a bummer... I've been using Android and have always had ROOT and all the goodies that come with it. And I recently starting really enjoying my Note 4 with all the cool development in Note 7 ported roms oh well... I wonder if the S7E is enough of an upgrade to keep my interest as stock?
I see there is a G935U firmware, but that seems a bit hit and miss? But I'm just starting to read up on all this... :good:
ShrekOpher said:
Get a One+ 3T good development and really nice phone if you want root. Root is dead on Samsung phones and so are ROMs.
Click to expand...
Click to collapse
Believe me bud, if Oneplus 5 or even 3T had an SD Card, I'd already have that phone, but thanks for your wisdom !
Araltd said:
So by reading thru this thread, I assume having a T-mobile S7E (G935T) rooting is pointless and really not available the way I'm used to it coming from a Note 4. That's kind of a bummer... I've been using Android and have always had ROOT and all the goodies that come with it. And I recently starting really enjoying my Note 4 with all the cool development in Note 7 ported roms oh well... I wonder if the S7E is enough of an upgrade to keep my interest as stock?
I see there is a G935U firmware, but that seems a bit hit and miss? But I'm just starting to read up on all this... :good:
Click to expand...
Click to collapse
You and I both man... The last few years, I have lived off the mercy of T-Mobile and their BLs being unlocked. But Samsung sure done them all in ! Even the International unlocked ones disable Samsung Pay (forever, mind you!) if Knox is tripped, which I believe it is, when rooted and TWRP'd.
As I understand it,
Android pay / Samsung pay is why they frown on rooting now. I can understand it, though I don't agree with it.
The first time someone's financial information is compromised, and they've ever used one of the "pay" methods, on a rooted device the pr nightmare that would ensue would make the note 7 fiasco look like child's play.
"Samsung unsecured device compromises persons credit card information today, while Apple is still secure" I can see the headline.
Sent from my Samsung Galaxy S7E
Hi, all!
I bought the Blade X Max from Cricket, as it's got 32GB internal storage, a bigger screen, and seems a very hip machine.
Since Cricket seems to have instructed the various vendors, LG, Alcatel, and now ZTE to not only just make it difficult to root, but near-impossible, at least for someone without extensive knowledge as an Android dev, it's an annoyance...
There are legit, non-bootleg apps for which I spent good money (Titanium, Apps2SD Pro, FlashFire and others), which require root... Unlocking codes tend to be expensive, and the sites that offer them seem more spam-generators than anything else, and the Dr.Fone Root tool doesn't seem to even know the device exists, and, it's as yet not on their supported list, that I can see.
The device was released a month ago, so I'm not expecting immediate miracles, but wondering if anyone else owns the device, and if anyone with the dev chops would be interested in exploring the possibility.
Thanks for reading, and have a great day!
I own the ZTE Blade X Max as well, I havent tried root or anything else yet, I was a little surprised though when searching through XDA and this thread was all I found in relation to the ZTE Blade X Max.
XperianceIT said:
I own the ZTE Blade X Max as well, I havent tried root or anything else yet, I was a little surprised though when searching through XDA and this thread was all I found in relation to the ZTE Blade X Max.
Click to expand...
Click to collapse
Well, since the device has only been around a few months, it's understandable that not a lot of the devs have access to one, but, yeah... All over the web, it's referred to as a carrier-branded phone, and people seem to not want to fiddle with it...
I don't need a custom ROM, but there are legit apps that I bought from the Play Store, and they require root...
I blame Cricket for being paranoid that someone would dare to customize her/his phone and tweak it... Times past, Cricket made it difficult to root a phone, but the LG G-Stylo was pretty much unrootable... I have a few paperweights of that model in my storage... The Idol 3 was able to be rooted, the 6055U Idol 4, not so much... and now this one... It seems that Cricket is trying to have the various manufacturers leave some things out of their flavors of Android, so that even someone who reasonably is willing to take the risk is sh!t out of luck... <sigh>
Yeah Cricket has been making it real hard to root any of their phones. I also have the Stylo 2, and they had lg remove the entire bootloader and stock recovery, how the hell that was possible is beyond me. Get used to this trend in Android, it's not just Cricket, allot of flagships are doing what they can to get rid of the ability to root, cause if we root we have control not them, and the manufacturers are making way to much in terms of ad revenue to allow us to have total control. My Blade X Max will sometimes randomly download apps and games without my permission, that's how they ( manufacturers ) make the money they do, we are basically walking billboards for them. So unless enough people get together and complain about the blatent abuse of the GPL Linux has laid out, it will never change, open source my ass, try getting the real source code for this phone, won't happen. I downloaded the source for the max x 2 and dug into the files, wasn't even the full code, and had junk files from dead devices. The Android world is not what it's supposed to be, get used to it.
zMILWAUKEE said:
Yeah Cricket has been making it real hard to root any of their phones. I also have the Stylo 2, and they had lg remove the entire bootloader and stock recovery, how the hell that was possible is beyond me. Get used to this trend in Android, it's not just Cricket, allot of flagships are doing what they can to get rid of the ability to root, cause if we root we have control not them, and the manufacturers are making way to much in terms of ad revenue to allow us to have total control. My Blade X Max will sometimes randomly download apps and games without my permission, that's how they ( manufacturers ) make the money they do, we are basically walking billboards for them. So unless enough people get together and complain about the blatent abuse of the GPL Linux has laid out, it will never change, open source my ass, try getting the real source code for this phone, won't happen. I downloaded the source for the max x 2 and dug into the files, wasn't even the full code, and had junk files from dead devices. The Android world is not what it's supposed to be, get used to it.
Click to expand...
Click to collapse
Indeed...
Next time around, going to buy a pre-unlocked device (hell, even our local Walmart Super-aircraft hangar sells 'em), and just have the device ported over... if the vendor (Cricket, Metro, whomever) won't do it, they don't need my business... I'm a write-off from years back with Verizon, and, although my credit rating is much better these days, I worked for a Sprint call-center, and they sucketh verily and forsooth, and I don't know much about AT&T proper, or many other vendors...
But there are some vendors that are generally pretty hip, if a bit expensive, and I'm looking into seeing if, even if this is a vendor-branded device, there's a way, or just a straight-up trade for a device I can work with... Cricket's Android Nougat flavor is buggy as hell, and this is just kinda silly.
<sigh>
What the hell...
"Oh, Brave new world that hath such people in it.."
Wow are you serious? No root method? I'm going to have to sell this phone? WTF I just liked it.
Sent from my Z983 using Tapatalk
justlovejoy said:
Wow are you serious? No root method? I'm going to have to sell this phone? WTF I just liked it.
Sent from my Z983 using Tapatalk
Click to expand...
Click to collapse
Well, apparently the bootloader's crippled, as Cricket seems to have insisted things be removed from ZTE's source code...
But, I'm wondering (though I might just be talking out my butt), if the code module could be extracted from ZMax Pro, as that's apparently its non-Cricket branded twin...
My coding chops are limited to old XBASE and a bit of Delphi/FPC, so I'm not the guy to do it, but am I in the ballpark with my idea?
Never really messed with the bootloader. I've always been developing from code tho. Haven't tinkled too much in about a year but need a laptop power cord before I can try anything. Bootloader isn't always a root blocker. It's more of a custom rom blocker if memory hasn't been affected by times changing
Sent from my Z983 using Tapatalk
justlovejoy said:
Never really messed with the bootloader. I've always been developing from code tho. Haven't tinkled too much in about a year but need a laptop power cord before I can try anything. Bootloader isn't always a root blocker. It's more of a custom rom blocker if memory hasn't been affected by times changing
Sent from my Z983 using Tapatalk
Click to expand...
Click to collapse
Well, again, my chops are decades old, and tend to involve xBASE and Delphi coding, and I know very little about C/C++ and Java, and plead ignorance of what Cricket has insisted on having crippled in the source, and I lean on the expertise of devs here and elsewhere for that reason...
Just that it's one helluva device, or would be if it could be at least rooted.... I just don't know how... :laugh:
pauljulian said:
Well, again, my chops are decades old, and tend to involve xBASE and Delphi coding, and I know very little about C/C++ and Java, and plead ignorance of what Cricket has insisted on having crippled in the source, and I lean on the expertise of devs here and elsewhere for that reason...
Just that it's one helluva device, or would be if it could be at least rooted.... I just don't know how... [emoji23]
Click to expand...
Click to collapse
Facts!
That's what the kids say today, lol. It's a beauty. Had to get mine swapped out for another due to the fingerprint reader and camera being intermittent between reboots. Not much I can say wrong about this device. Waiting on the key to the mailbox for my laptop charger still. Can't promise anything yet but I'm hopeful that our resources will get us started, even if it's just a long list of what doesn't work. Lmfao
Sent from my Z983 using Tapatalk
Is there anything we can do to this phone? Any thing
Sent from my Z983 using XDA-Developers Legacy app
Yes I have z982 and would like a forums section
Bootloader and recovery
zMILWAUKEE said:
Yeah Cricket has been making it real hard to root any of their phones. I also have the Stylo 2, and they had lg remove the entire bootloader and stock recovery, how the hell that was possible is beyond me. Get used to this trend in Android, it's not just Cricket, allot of flagships are doing what they can to get rid of the ability to root, cause if we root we have control not them, and the manufacturers are making way to much in terms of ad revenue to allow us to have total control. My Blade X Max will sometimes randomly download apps and games without my permission, that's how they ( manufacturers ) make the money they do, we are basically walking billboards for them. So unless enough people get together and complain about the blatent abuse of the GPL Linux has laid out, it will never change, open source my ass, try getting the real source code for this phone, won't happen. I downloaded the source for the max x 2 and dug into the files, wasn't even the full code, and had junk files from dead devices. The Android world is not what it's supposed to be, get used to it.
Click to expand...
Click to collapse
First off they can't remove the bootloader as android WON'T boot without it, and recovery is needed for factory resets. Cricket has never been helpful about supporting their phones, but of you do a search you can find out how to get into the recovery. (And it's the ZTE Blade ZMax, not X Max, X Max is just crickets version of the Blade ZMax)
To get into recovery you can go to this link for instructions
http://www.hardreset.info/devices/zte/zte-blade-x-max-z983/recovery-mode/
revjamescarver said:
First off they can't remove the bootloader as android WON'T boot without it, and recovery is needed for factory resets. Cricket has never been helpful about supporting their phones, but of you do a search you can find out how to get into the recovery. (And it's the ZTE Blade ZMax, not X Max, X Max is just crickets version of the Blade ZMax)
To get into recovery you can go to this link for instructions
http://www.hardreset.info/devices/zte/zte-blade-x-max-z983/recovery-mode/
Click to expand...
Click to collapse
Have always been able to get into the stock recovery, and the download mode... those are not the issues, friend....
Whatever Cricket specified be done to their stock ROM by ZTE, we're blocked from doing those things that would enable us to actually use legit apps that we paid real money for.
I don't care about any sort of custom ROM, as these days, I really don't have the time to **** with it... But I've been an Android user for years... I've no problem rooting a device, given a workable method, and at least nutshell instructions, and doing a few things, as a user... As long as there is a way to get back to Square 1, should I screw up, I'm not afraid to explore, and, again, I believe in supporting good developers... If an app does what I want it to, I buy it, as long as it doesn't break the bank... in that case, I uninstall and find something better or cheaper...
But Cricket, in their either paranoia, or control freak attitude has been progressively making their devices less and less possible to do what we bought them for, unless we happen to be Cricket employees, sworn to secrecy regarding those codes beneath and behind the *# ones that really don't do much, at least not the ones we need to use, such as the menu option for "unlock" which doesn't without other input...
pauljulian said:
Have always been able to get into the stock recovery, and the download mode... those are not the issues, friend....
Whatever Cricket specified be done to their stock ROM by ZTE, we're blocked from doing those things that would enable us to actually use legit apps that we paid real money for.
I don't care about any sort of custom ROM, as these days, I really don't have the time to **** with it... But I've been an Android user for years... I've no problem rooting a device, given a workable method, and at least nutshell instructions, and doing a few things, as a user... As long as there is a way to get back to Square 1, should I screw up, I'm not afraid to explore, and, again, I believe in supporting good developers... If an app does what I want it to, I buy it, as long as it doesn't break the bank... in that case, I uninstall and find something better or cheaper...
But Cricket, in their either paranoia, or control freak attitude has been progressively making their devices less and less possible to do what we bought them for, unless we happen to be Cricket employees, sworn to secrecy regarding those codes beneath and behind the *# ones that really don't do much, at least not the ones we need to use, such as the menu option for "unlock" which doesn't without other input...
Click to expand...
Click to collapse
... and just to say that I know that "unlock" and "root" are two different things... was just an example.
pauljulian said:
Have always been able to get into the stock recovery, and the download mode... those are not the issues, friend....
Whatever Cricket specified be done to their stock ROM by ZTE, we're blocked from doing those things that would enable us to actually use legit apps that we paid real money for.
I don't care about any sort of custom ROM, as these days, I really don't have the time to **** with it... But I've been an Android user for years... I've no problem rooting a device, given a workable method, and at least nutshell instructions, and doing a few things, as a user... As long as there is a way to get back to Square 1, should I screw up, I'm not afraid to explore, and, again, I believe in supporting good developers... If an app does what I want it to, I buy it, as long as it doesn't break the bank... in that case, I uninstall and find something better or cheaper...
But Cricket, in their either paranoia, or control freak attitude has been progressively making their devices less and less possible to do what we bought them for, unless we happen to be Cricket employees, sworn to secrecy regarding those codes beneath and behind the *# ones that really don't do much without other input...
Click to expand...
Click to collapse
I'm not sure how you would root that particular phone, but I'm sure there is a way, or will be once the phone is out there longer, being without root access is a pain in the a**
revjamescarver said:
I'm not sure how you would root that particular phone, but I'm sure there is a way, or will be once the phone is out there longer, being without root access is a pain in the a**
Click to expand...
Click to collapse
When I originally started the thread, yep... I know the thing's not been out long... like since May (and I know crap all about the "Z" model used by other vendors... Obviously there's a drastic difference in the firmware, though...)...
Given time, I'm certain someone will work it out... There's a gentleman on another thread that seems to be working on it, and I'm going under the thing of "no news is good news" :laugh:
I've no doubt there's a way... I did a short stint at a call-center for Sprint, and there are always ways... It's a matter of having the right set of input codes, to get to the means to do the real deal...
I really dig the phone, although Cricket's flavor of Nougat isn't the most stable in the world... but, with the legal and legit apps I bought and continue to support, that's less of an issue.
It's frustrating when a company knows what a pain in the ass it is without allowing the user to administer it as really needs be... and they still refuse to permit it... I get that turning it into a paperweight can get tedious, but, given the means to get it back to factory standard in a reasonably simple way without sending it in, or buying another is just what I would see as normal... It's my own fault if I haven't backed up my data, but, if I somehow hose the firmware, just give me a means to get back to the start... It worked with their edition of the the Alcatel Idol 3... the Idol 4 (6055U)... I just gave the hell up.
pauljulian said:
When I originally started the thread, yep... I know the thing's not been out long... like since May (and I know crap all about the "Z" model used by other vendors... Obviously there's a drastic difference in the firmware, though...)...
Given time, I'm certain someone will work it out... There's a gentleman on another thread that seems to be working on it, and I'm going under the thing of "no news is good news" :laugh:
I've no doubt there's a way... I did a short stint at a call-center for Sprint, and there are always ways... It's a matter of having the right set of input codes, to get to the means to do the real deal...
I really dig the phone, although Cricket's flavor of Nougat isn't the most stable in the world... but, with the legal and legit apps I bought and continue to support, that's less of an issue.
It's frustrating when a company knows what a pain in the ass it is without allowing the user to administer it as really needs be... and they still refuse to permit it... I get that turning it into a paperweight can get tedious, but, given the means to get it back to factory standard in a reasonably simple way without sending it in, or buying another is just what I would see as normal... It's my own fault if I haven't backed up my data, but, if I somehow hose the firmware, just give me a means to get back to the start... It worked with their edition of the the Alcatel Idol 3... the Idol 4 (6055U)... I just gave the hell up.
Click to expand...
Click to collapse
I don't mean to freak out anyone that "Holy Cr*p! Someone's doing something"
.... But I'm just wondering if anyone's doing something.... ?
It's not going to happen my best advice to you is get another phone. I have the z982 the z981,982,983 all of them are unrootable ZTE had a bad hack a few years back that almost shut them down root was giving full access to those phones through apps. I hate this phone and can't wait to get a new one. Never again will I buy ZTE
adambomb_13 said:
It's not going to happen my best advice to you is get another phone. I have the z982 the z981,982,983 all of them are unrootable ZTE had a bad hack a few years back that almost shut them down root was giving full access to those phones through apps. I hate this phone and can't wait to get a new one. Never again will I buy ZTE
Click to expand...
Click to collapse
Well, for damned sure I'm sick of Cricket's control freak practice...
But it seems there are too many vendors that undercut legitimate developers whose products require root access...
I don't really need a custom ROM, but I bought Apps2SD Pro, Titanium and some others because I found them to be well-written, well-designed, and they did what I needed them for... But, since I can't root this otherwise pretty cool device, I've basically wasted my $$... I'll get another device at some time, preferably from a vendor that is less paranoid about users actually using their devices to their potential, but for right now?
This is one of the most stupid situations I've found myself... A device that is capable of being a laptop replacement, but the vendor only insists on our using them as they dictate...
So, is disgust an applicable word?
... mind you, not at those among us who were suckered into buying a hip but crippled device.
(although I've the idea that those who actually work for Cricket but are sworn to secrecy by potential lawsuits and loss of employment actually have an idea as to whatever *# commands actually go deep enough to do what's needed)
But I have no issues with those such as I that found a really hip little machine, yet have found ourselves locked away from its potential...
My issues are with the control-freak assholes that set the policies for the companies we pay entirely too much to remain in necessary communication.
If Verizon users are still intrested, just take a look here:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
This guy J4NN is a genius!
Maybe for a bounty he will do it for your device. ?
Inerent said:
If Verizon users are still intrested, just take a look here:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
This guy J4NN is a genius!
Maybe for a bounty he will do it for your device.
Click to expand...
Click to collapse
I got a PM about Temp root for Verizon Google Pixel 2 XL, I guess it was due to this post of you, @Inerent.
It seems that instead of exchanging PMs, it would be better to post it here, to clarify the situation.
Hopefully this is ok with @trabadura, who contacted me.
trabadura said:
j4nn said:
trabadura said:
Hi j4nn, i see your post in xda for temp root Sony XZ1c with Snapdragon 835 and I figured you could help us for temp root Verizon Google Pixel 2 Xl for Unlock Bootloader?
Click to expand...
Click to collapse
Hi, I am not sure about that - I do not have that phone and cannot get/borrow it for testing either.
Do you know if it is possible to downgrade it's firmware?
Can you point me to earliest fw for download that it can be downgraded to?
What exactly the problem is - bootloader is not possible to unlock because Verizon (is it a mobile network operator?) disabled bootloader unlock possibility while on general not Verizon variant google allows it?
Is it also sim locked to Verizon operator only?
And how do you know that getting temp root would help you?
Click to expand...
Click to collapse
Hi, аs far as I know, it can not downgrade firmware with locked bootloader. With unlocked bootloader no problem.
The problem is in mobile operator. They lock option "OEM Unlock" (stay grayed out) in developer option. In general not Verizon variant no problem option is active and no problem to unlock bootloader. No sim locked only bootloader. Тhere is a lot of writing about the topic I can give a few links in the forum.
Links:
https://forum.xda-developers.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652
Click to expand...
Click to collapse
I am sorry, but in my opinion, you are out of luck.
At least if google/verizon delivers FOTA updates and most users accept them instead of staying at the version they bought the phone with.
You could get temp root only with some completely new not fixed kernel vulnerability which would not get patched for longer period of time and that's not happening very often.
If someone starts working on an exploit while most users upgrade in short time closing the bug being worked on, it does not make sense to put an effort into it.
To consider porting my work for other targets, you need to make sure you can run kernel which is still vulnerable to CVE-2017-7533 (race between inotify and rename) and few other CVEs that are needed to overcome android oreo mitigations. Google has patched the mentioned CVE which is the primary one with 2017-12-05 security patch level.
How many users do you think stay on older patch level than that? And would continue staying on it?
I am afraid nobody would help you no matter how much you promise with the bounty.
And so you know, working on it, only because of the bounty mostly is not worth it - at least in my case if I compare the lost time and what is promised in xperia xz1 bounty thread I would be better working any low paid job. That means if I did not want to get it done for myself, I would not work on it!
And even though Google Pixel 2 XL bounty is lot higher, the difficulty (due to no downgrade possibility) is extremely high and gets higher with each update.
I am afraid you need to get used to the fact that there never be a root for it, I am sorry.
You all should have probably bought the open (not Verizon locked) variant instead or be satisfied with the product as bought (I guess it must have been a great deal, right?).
Or at least educate all users here not to allow any upgrade at all since beginning (if that's even possible to disable the updates).
j4nn said:
I got a PM about Temp root for Verizon Google Pixel 2 XL, I guess it was due to this post of you, @Inerent.
It seems that instead of exchanging PMs, it would be better to post it here, to clarify the situation.
Hopefully this is ok with @trabadura, who contacted me.
I am sorry, but in my opinion, you are out of luck.
At least if google/verizon delivers FOTA updates and most users accept them instead of staying at the version they bought the phone with.
You could get temp root only with some completely new not fixed kernel vulnerability which would not get patched for longer period of time and that's not happening very often.
If someone starts working on an exploit while most users upgrade in short time closing the bug being worked on, it does not make sense to put an effort into it.
To consider porting my work for other targets, you need to make sure you can run kernel which is still vulnerable to CVE-2017-7533 (race between inotify and rename) and few other CVEs that are needed to overcome android oreo mitigations. Google has patched the mentioned CVE which is the primary one with 2017-12-05 security patch level.
How many users do you think stay on older patch level than that? And would continue staying on it?
I am afraid nobody would help you no matter how much you promise with the bounty.
And so you know, working on it, only because of the bounty mostly is not worth it - at least in my case if I compare the lost time and what is promised in xperia xz1 bounty thread I would be better working any low paid job. That means if I did not want to get it done for myself, I would not work on it!
And even though Google Pixel 2 XL bounty is lot higher, the difficulty (due to no downgrade possibility) is extremely high and gets higher with each update.
I am afraid you need to get used to the fact that there never be a root for it, I am sorry.
You all should have probably bought the open (not Verizon locked) variant instead or be satisfied with the product as bought (I guess it must have been a great deal, right?).
Or at least educate all users here not to allow any upgrade at all since beginning (if that's even possible to disable the updates).
Click to expand...
Click to collapse
You are completely right. And that is the difference between Android and iPhone communities. Every Android user prefer to stay aside of this problem, naively thinking that they would not be affected. In Oreo Google has already put all the Root CAs into the System storage. So Nobody knows what kind of data the phone uploads every day to 3rd party servers. Verizon is just an example there are many companies who do the same. iPhone community is great because everybody know that some day under certain circumstances they can lost their JB. I hope one day some mid-range iOS developer will buy Android phone and start developing a great root tools. Sure it will be quite easy because all the source code is available.
I appreciate your work. Thank you and good luck.
First they came for the socialists, and I did not speak out—
Because I was not a socialist.
Then they came for the trade unionists, and I did not speak out—
Because I was not a trade unionist.
Then they came for the Jews, and I did not speak out—
Because I was not a Jew.
Then they came for me—and there was no one left to speak for me.