Huawei Elate / Ascend XT2 - Lollipop - Huawei Ascend XT Questions & Answers

Doe anyone have a tutorial on how I can roll the Elate back to Lollipop? I have unlocked it with fasboot but thats as far as I got...any help would be really appreciated, dont know where else to look.

If you just unlocked the bootloader, then the phone should still have stock Nougat, so there's nothing to roll back to. And this phone never had Lollipop - not sure where that idea came from.
vrdubb02 said:
Doe anyone have a tutorial on how I can roll the Elate back to Lollipop? I have unlocked it with fasboot but thats as far as I got...any help would be really appreciated, dont know where else to look.
Click to expand...
Click to collapse

vrdubb02 said:
Doe anyone have a tutorial on how I can roll the Elate back to Lollipop? I have unlocked it with fasboot but thats as far as I got...any help would be really appreciated, dont know where else to look.
Click to expand...
Click to collapse
Could I ask,why move back to lollipop..? I can understand aversion to change, but not much has changed from nougat to lollipop that's not arguably much better. App permissions are quite a bit tightened up, which can break old crappy apps.. For example, airplane mode and other radio settings can no longer be changed by any app, and requires root permissions past kitkat. It's slightly more annoying for me to set up automated tasks to change those settings, but I'd much rather go through that hassle than leave all settings unprotected..
Fwiw, I wouldn't get your hopes up.. 18 months after the first ascend was released, we still have not received the proper source files to create custom roms, and it's becoming increasingly less likely we ever will. In your case, these files would need to be available and there would need to be a developer willing to compile lollipop, a version many years outdated, when most will be attempting to port oreo and newer versions.
Perhaps if we knew why you need lollipop,we could help with a workaround, though likely you won't have much luck until someone gets twrp working..

Essentially this is to be a dedicated device for flying a DJI Phantom drone and their app is more stable on lollipop whisch is why I wanted to change it. I have been doing some research but coming up short so either I just use it as is or if it gets bad I'll just get a used more popular device. Thank you for be feedback.

If you need real-time control of something, I don't know if I could recommend this device. With a few governor tweaks this phone can be pretty zippy, but emui is about as janky as oem roms work.
If you want a dedicated device that you aren't planning on bloating up.. look around for a used galaxy s4 or s5, or an s3 even (any older phone with a snapdragon 800 series, really). They can be had for pretty dang cheap, and a 4-5 year old flagship will prove much faster than even a brand new low end device - especially if you are looking for something with lollipop.

Related

[Q] 4.2 rooted or 4.4 update?

So with the inevitable release of KitKat tomorrow, I have the quandary of upgrading or not. I understand the 4.4 will kill my root, but I really haven't used the root option due to interceding life getting in the way since I rooted it (originally I was going to use Ti Backup and go from there, but have never bought it). So losing root is not a huge deal breaker one way or another currently.
With the leaked build, does it look like a good update to do or has the current ROM users of KitKat feel it's not worth it? I'd like to get some input to help make up my mind...
scottiemedic said:
So with the inevitable release of KitKat tomorrow, I have the quandary of upgrading or not. I understand the 4.4 will kill my root, but I really haven't used the root option due to interceding life getting in the way since I rooted it (originally I was going to use Ti Backup and go from there, but have never bought it). So losing root is not a huge deal breaker one way or another currently.
With the leaked build, does it look like a good update to do or has the current ROM users of KitKat feel it's not worth it? I'd like to get some input to help make up my mind...
Click to expand...
Click to collapse
I own both an I337 and an M919 and, given the flexibility of the M919, I was able to try both official and leaked 4.4 TW releases mainly for the I9505. Based on those experiences I would say take the update. 4.4 update should be noticeably faster.
In regard to keeping root, I'm hoping SuperSu Pro's Survival mode works.
I'd say go with the update if you don't care about root. The only problem is Knox is more locked down, also more bloat/crap ware on the new update. I do love the camera on the lockscreen, plus the album artwork on the lock screen is a big + for me. I don't know if art is implemented into the gs4 but it does make a difference but the only thing is, is that most apps are not optimized for it yet.
Sent from my XT1058 using xda premium
So should I revert the few changes I have done? IE, I've killed startup apps with ES Task Manager and (obviously) disabled the software update checker.
I'm on the original/not locked down 4.2.2. What do I need to do, to accept the update? I too found that I don't use Root much, but T.B. would be nice to have. I have clockword installed now as a bootloader, so maybe I need to revert to stock bootloader somehow. Previous OTA's have failed.
As far as experience goes, I say wait and keep your options open. I like the freedom of a clean rom, free from bloat and clutter of apps that i dont use. Not to mention a battery life that exceeds far beyond a regular un-rooted device. Visit the numerous threads of other people's experiences. I'm rooted and have been able to try out different rooms from 4.2 to 4.4. Accepting an ota will unroot your device without anyway of reverting back. Good luck with your decision.
Sent from my GT-I9505 using XDA Premium 4 mobile app
aiwapro said:
I'm on the original/not locked down 4.2.2. What do I need to do, to accept the update? I too found that I don't use Root much, but T.B. would be nice to have. I have clockword installed now as a bootloader, so maybe I need to revert to stock bootloader somehow. Previous OTA's have failed.
Click to expand...
Click to collapse
If you're on the not locked down version, then you shouldn't take the update. It will lock your bootloader and that device will never see an AOSP ROM again. You should wait for something like StockUp to be updated to the new 4.4 or use any of the many other 4.4 ROMs available. If you really want to get one with the stock update and locked bootloaders, I'm sure someone would love to trade.
aiwapro said:
I'm on the original/not locked down 4.2.2. What do I need to do, to accept the update? I too found that I don't use Root much, but T.B. would be nice to have. I have clockword installed now as a bootloader, so maybe I need to revert to stock bootloader somehow. Previous OTA's have failed.
Click to expand...
Click to collapse
We were able to get the MK2 tar files rather quickly after the OTA release and will hopefully be able to get the 4.4 tars just as quickly. If that's the case you will be able to flash all partitions, except the bootloader, to run the 4.4 ROM and keep your unlocked bootloader. I would not give up the unlocked bootloader if I were you.
scottiemedic said:
So with the inevitable release of KitKat tomorrow, I have the quandary of upgrading or not. I understand the 4.4 will kill my root, but I really haven't used the root option due to interceding life getting in the way since I rooted it (originally I was going to use Ti Backup and go from there, but have never bought it). So losing root is not a huge deal breaker one way or another currently.
With the leaked build, does it look like a good update to do or has the current ROM users of KitKat feel it's not worth it? I'd like to get some input to help make up my mind...
Click to expand...
Click to collapse
Sounds like you are not someone that really uses or needs root like us flashaholics. I love having complete control over my devices. The extraordinary battery life, increased performance, extra capabilities like tethering and so forth. If I want to delete an un-wanted app or service ( At&t navigator anyone) or try a new rom I can. With a stock rom with locked boot loaders (really an oxymoron for "open source" Android isn't it?) you have what you get, like it or not. It's sad they load these awesome devices up with so much performance killing bloat ware. It's like buying a new corvette & then attaching a loaded u-haul trailer to it. What's the point of having it if you can't use it as intended? Anyway my 2 cents worth. Choose your path wisely grasshopper, as there's no turning back.
Hello everyone!
I have been thinking about getting myself one of these lovely phones but after reading what y'all have been saying about the locked bootloader I'm not sure I want to... I won't be able to actually get a phone until next week so I'm assuming it will come already pre-loaded with this update??
I would like to be able to root this phone just like I did my old ET4G from Sprint... would this be an option if I was to get one next week?
Just an FYI I will be on the AT&T network.
ttfn
CDL
crazy_dragonlady said:
Hello everyone!
I have been thinking about getting myself one of these lovely phones but after reading what y'all have been saying about the locked bootloader I'm not sure I want to... I won't be able to actually get a phone until next week so I'm assuming it will come already pre-loaded with this update??
I would like to be able to root this phone just like I did my old ET4G from Sprint... would this be an option if I was to get one next week?
Just an FYI I will be on the AT&T network.
ttfn
CDL
Click to expand...
Click to collapse
Get a nexus 5. You'll love it
Sent from my Nexus 5
jd1639 said:
Get a nexus 5. You'll love it
Sent from my Nexus 5
Click to expand...
Click to collapse
AT&T doesn't offer that phone... unless I'm just not seeing it LOL
crazy_dragonlady said:
AT&T doesn't offer that phone... unless I'm just not seeing it LOL
Click to expand...
Click to collapse
They don't but it works fine on att. Very easy to root and mod. No locked bootloader.
Sent from my Nexus 5
John The Rhino said:
Sounds like you are not someone that really uses or needs root like us flashaholics. I love having complete control over my devices. The extraordinary battery life, increased performance, extra capabilities like tethering and so forth. If I want to delete an un-wanted app or service ( At&t navigator anyone) or try a new rom I can. With a stock rom with locked boot loaders (really an oxymoron for "open source" Android isn't it?) you have what you get, like it or not. It's sad they load these awesome devices up with so much performance killing bloat ware. It's like buying a new corvette & then attaching a loaded u-haul trailer to it. What's the point of having it if you can't use it as intended? Anyway my 2 cents worth. Choose your path wisely grasshopper, as there's no turning back.
Click to expand...
Click to collapse
I guess I've just never gotten any real good info on WHAT my rooted GS4 can do. I'd love to extend battery life and tether, but without really knowing all the possible downfalls, I've never pulled the trigger on like system apps, bloatware, etc. You know of a good resource for slightly technical people with clear definitions of what certain programs do and what can and can't be deleted?
I think at the time I rooted (I'm a MF3 S4), there was no 'unrooting' or flashing to stock, and therefore have been reluctant. I know I don't spend enough time on here learning, my 5 and 2 year old suck all my extra time away.
I'd love to maximize my phone to it's greater abilities, just overwhelmed I guess on where to start as I'm perfectly happy on 4.2 (I owned 3 iPhones before getting this one, so I have limited Android experience, but I recently also got an ASUS TF300 and rooted and ROMed my Kindle Fire almost 2 years ago to CM9).
scottiemedic said:
I guess I've just never gotten any real good info on WHAT my rooted GS4 can do. I'd love to extend battery life and tether, but without really knowing all the possible downfalls, I've never pulled the trigger on like system apps, bloatware, etc. You know of a good resource for slightly technical people with clear definitions of what certain programs do and what can and can't be deleted?
I think at the time I rooted (I'm a MF3 S4), there was no 'unrooting' or flashing to stock, and therefore have been reluctant. I know I don't spend enough time on here learning, my 5 and 2 year old suck all my extra time away.
I'd love to maximize my phone to it's greater abilities, just overwhelmed I guess on where to start as I'm perfectly happy on 4.2 (I owned 3 iPhones before getting this one, so I have limited Android experience, but I recently also got an ASUS TF300 and rooted and ROMed my Kindle Fire almost 2 years ago to CM9).
Click to expand...
Click to collapse
Hey man, no worries. The reality is I would much rather play with my kids (if I had any) than an electronic device. So it's nice to know your priorities are right. There's few picture worthy moments we get from our phones, but kids provide such memories constantly. For everyday use, stock is fine & was for me for a little while. You are doing the right thing by waiting until you know more before you do something wrong & brick your phone. This is the place where you can learn how to root, install Safestrap recovery & flash incredible custom rom on your mf3 S4 when you are ready.

All things root and Bootloader?

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

LS997 LG V20 Root/Unroot Questions (Sprint)

So i would really like to root my LS997 (Sprint) LG V20, my only concern is there is no way back once rooted so if something happens to my phone and need to take it in the the store im pretty much screwed... so is it really worth rooting at this time without a way to go back to? Also would be the best way to root if i did decide to root this device (Link) would be greatly appreciated.. Thanks everyone!!
This is my 2 cents. I have previously rooted phones before as well as this phone, but I can't honestly say that I would recommend it. Don't get me wrong, the unlocking/rooting method (Dirty Santa) is straight forward and the support you get here on XDA is second to none, but if you're catious about not being able to go back to stock you may want to hesitate. You need to consider the pro's and con's and figure out for yourself what you want. I wanted to be able to reboot my phone without a static boot screen. I wanted to be able to update OTA the day the updates were available and to not rely on someone getting a clean update image, etc. I didn't see the benefit of the mods that are currently available, and the promise of getting all the stock LG apps to work on a Sprint phone is not 100% true. You can get some to work without root. There were several that still did not work (if that matters to you). Thankfully my phone glitched out and wouldn't boot, so Sprint offered me an exchange which I happily accepted. Let's just say that rooting on the Sprint variant is not for the faint of heart and you better not expect to need to send your phone in for any repairs as well. Bottom line, if it's your DD and you can't do without, I can't recommend rooting at this time. Just my 2 cents...
EDIT: For me to root again, I would need to have a bona fide working KDZ to return to stock and LineageOS to release an official ROM for LS997 that utilizes the second screen (I like it, so piss off, lol).
Ok so in a nut shell .. I should really just wait for a way to go back if needed ?
Spanky' said:
Ok so in a nut shell .. I should really just wait for a way to go back if needed ?
Click to expand...
Click to collapse
NO,
You need to accept two things.
1.) Currently if you root, you will not have a way to go back to FULLY stock and locked, but thats no fun anyways lol,
The real issue with this isn't going back to "stock" but having a "kdz" avalible for the recovery of a hard bricked device, or a soft brick that you cant understand how to fix. This is a restore img that you use a pc to push to phone to update, downgrade, or restore a lg phone, and sadly Sprint wont be releasing a kdz publicly, and its not coming so dont ask for a eta .
2.) The dreaded static on the bootup screen. We lack the developers on the Sprint/LG side of things that work on boot.img's,
This puts a ton of V20 users sprint and others in a bad spot. Where once ur rooted, you have static, and thats gonna ALWAYS be the case, unless you flash a AOSP rom like lineage. For this one, its just a nucence issue on reboots, its not really a issue for use, but man i can say I do miss having a custom boot animation on a reboot ( The static covers up the boot logo etc until you lock your screen)
The rest is regular root stuff. Some bugs etc. As far as getting LG apps back, and 2nd screen support..
The stock lg apps are back, and working as far as im aware. At-least on my rom ive brought back 99% of lgs apps that were gone, but some i didn't care to bring back. Like LG calculator and LG calendar. The Google replacement is better and more synchronization. But things like LG gallery and lg stock messages were things that should have never been pulled, and LG did in fact put them back on their G6. Smart move lg. There isn't any stock apps im aware of that wont come back at this stage.
2nd screen is proprietary, so unless devs build their own app using the 2nd screen code on lineage is stealing and xda wont accept that. So if ur leaving lgs softwear to flash a aosp rom you knew going into this that 2nd screen isnt a option, and if untimately your looking for pure android you should get the pixel xl or equivalent pure device.
There are some things with Encryption that could cause issues, mostly for those using some sort of high end email that checks your device security may not work, but thats going to be any rooted/unlocked device id say.
The statement : its not for the faint of heart: is kinda true. Rooting isn't for some, and you better be able to read/follow instrucions that are provided, and make sure you have a grasp before starting.
There is a ton of info on the site for users to read and digest as well as the V20 section has stayed pretty active with users and devs alike, myself being the latter. There's hope on the horizon for the above mentioned. Both KDZ and Static are works in progress, and unless a dev who is knowledgeable on these things comes over to the device its the same og team working towards perfection.
As far as OTA updates go, there are 0 devices on the market that get software updates from the manufacture after you have modified your system etc. This isnt just manufacture hating on the root, but also avoiding bricking ur custom device with a block update that is targeting files that are gone/moved/changed. So dont worry about ota updates as they are gonna break everywhere on anything that's rooted. The ota updates get pulled by devs, tested and implimented as fast as we can, but if you want the updates as the launch then dont root and accept the device as is. 99% of the time the bennifits of fixing / changing all the other things on the device to be delayed on a ota is worth it. Sprint is the 1st V20 to get onto the Feb Sec. Patch, all other carriers are still on Dec or older. But the update came for the sprint V20, and within 30days of it being live, weve managed to get the ota pushed to our rooted users and its working GREAT!
I can say 1 thing for sure, if you update your V20 to zv6 without being rooted 1st this debate is over anyways as it wont/cant be rooted anymore and the decision is gone to do so. But otherwise, theres a reason youve landed on xda, wondering about what the hype is about rooting etc, ill just leave a screenshot of my device here for looks. Im very proud of the work myself and the rest of the community has done. The device runs 10x faster and longer then the OEM;s software the released, and so many little bugs etc have been fixed also on our end to enhance it further. With the countless options to theme, customize and change ur device, the learning and experience itself is $$.
Ultimately, i vote to root the $H!T out of your phone, and worst case, get it replaced and do it again if you F it up!
Team DevDigitel said:
NO,
You need to accept two things.
1.) Currently if you root, you will not have a way to go back to FULLY stock and locked, but thats no fun anyways lol,
The real issue with this isn't going back to "stock" but having a "kdz" avalible for the recovery of a hard bricked device, or a soft brick that you cant understand how to fix. This is a restore img that you use a pc to push to phone to update, downgrade, or restore a lg phone, and sadly Sprint wont be releasing a kdz publicly, and its not coming so dont ask for a eta .
2.) The dreaded static on the bootup screen. We lack the developers on the Sprint/LG side of things that work on boot.img's,
This puts a ton of V20 users sprint and others in a bad spot. Where once ur rooted, you have static, and thats gonna ALWAYS be the case, unless you flash a AOSP rom like lineage. For this one, its just a nucence issue on reboots, its not really a issue for use, but man i can say I do miss having a custom boot animation on a reboot ( The static covers up the boot logo etc until you lock your screen)
The rest is regular root stuff. Some bugs etc. As far as getting LG apps back, and 2nd screen support..
The stock lg apps are back, and working as far as im aware. At-least on my rom ive brought back 99% of lgs apps that were gone, but some i didn't care to bring back. Like LG calculator and LG calendar. The Google replacement is better and more synchronization. But things like LG gallery and lg stock messages were things that should have never been pulled, and LG did in fact put them back on their G6. Smart move lg. There isn't any stock apps im aware of that wont come back at this stage.
2nd screen is proprietary, so unless devs build their own app using the 2nd screen code on lineage is stealing and xda wont accept that. So if ur leaving lgs softwear to flash a aosp rom you knew going into this that 2nd screen isnt a option, and if untimately your looking for pure android you should get the pixel xl or equivalent pure device.
There are some things with Encryption that could cause issues, mostly for those using some sort of high end email that checks your device security may not work, but thats going to be any rooted/unlocked device id say.
The statement : its not for the faint of heart: is kinda true. Rooting isn't for some, and you better be able to read/follow instrucions that are provided, and make sure you have a grasp before starting.
There is a ton of info on the site for users to read and digest as well as the V20 section has stayed pretty active with users and devs alike, myself being the latter. There's hope on the horizon for the above mentioned. Both KDZ and Static are works in progress, and unless a dev who is knowledgeable on these things comes over to the device its the same og team working towards perfection.
As far as OTA updates go, there are 0 devices on the market that get software updates from the manufacture after you have modified your system etc. This isnt just manufacture hating on the root, but also avoiding bricking ur custom device with a block update that is targeting files that are gone/moved/changed. So dont worry about ota updates as they are gonna break everywhere on anything that's rooted. The ota updates get pulled by devs, tested and implimented as fast as we can, but if you want the updates as the launch then dont root and accept the device as is. 99% of the time the bennifits of fixing / changing all the other things on the device to be delayed on a ota is worth it. Sprint is the 1st V20 to get onto the Feb Sec. Patch, all other carriers are still on Dec or older. But the update came for the sprint V20, and within 30days of it being live, weve managed to get the ota pushed to our rooted users and its working GREAT!
I can say 1 thing for sure, if you update your V20 to zv6 without being rooted 1st this debate is over anyways as it wont/cant be rooted anymore and the decision is gone to do so. But otherwise, theres a reason youve landed on xda, wondering about what the hype is about rooting etc, ill just leave a screenshot of my device here for looks. Im very proud of the work myself and the rest of the community has done. The device runs 10x faster and longer then the OEM;s software the released, and so many little bugs etc have been fixed also on our end to enhance it further. With the countless options to theme, customize and change ur device, the learning and experience itself is $$.
Ultimately, i vote to root the $H!T out of your phone, and worst case, get it replaced and do it again if you F it up!
Click to expand...
Click to collapse
Thank you for your detailed and informative reply... Im no newb to flashinging.. And understand the risks involved in rooting this perticular decive... As ive rooted many before.. Im on zv6 so it looks as though i cant root anywaus... Maybe some day we will get some kind of root and unroot... Hopefull thinking hahah ... But ya... Defiantly thinking about going back to samsung next upgrade...
My V20 was an absolute DOG before I rooted.
It was SLOOOOOOOOOW. The only thing that was fast was the battery draining.
Since rooting it is like night and day. Fast and battery last great.
midmadn said:
My V20 was an absolute DOG before I rooted.
It was SLOOOOOOOOOW. The only thing that was fast was the battery draining.
Since rooting it is like night and day. Fast and battery last great.
Click to expand...
Click to collapse
To bad im on zv6 i cant root this
I rooted with Dirty Santa. While it was easy to do, I misread or missed a step, no problems though.
I like being able to get rid of all the LG and Sprint apps, drives me crazy that they sit there even though I have 96GB space on my phone.
The static on boot up isn't too bad, just don't ever let your phone die completely and don't reboot and it's not a bother. A few times I have let my phone go totally dead. Most of the time booting up is not an issue. Once or twice I couldn't get in. I had to remove my case, pull pull out the battery, and boot again.
I do miss getting OTA updates.. not only for security, but because when Android O comes out and I'm not able to update I'm going to feel I am missing something even if there's nothing much different.
yuppicide said:
I rooted with Dirty Santa. While it was easy to do, I misread or missed a step, no problems though.
I like being able to get rid of all the LG and Sprint apps, drives me crazy that they sit there even though I have 96GB space on my phone.
The static on boot up isn't too bad, just don't ever let your phone die completely and don't reboot and it's not a bother. A few times I have let my phone go totally dead. Most of the time booting up is not an issue. Once or twice I couldn't get in. I had to remove my case, pull pull out the battery, and boot again.
I do miss getting OTA updates.. not only for security, but because when Android O comes out and I'm not able to update I'm going to feel I am missing something even if there's nothing much different.
Click to expand...
Click to collapse
Im going to guess there will be a custom rom for android O availible before official comes out lol

Any hope in development?

In case you guys haven't figured it out yet, development, Imo, is dead. There isn't stable root, no rom development outside of slightly modded stuff to change your status bar and the most recent breakthrough was substratum... Which wasn't even meant for this phone but rather the s8 but it still works. Now I use and love substratum but I really want an aosp/pixel rom and stable root and Xposed but I don't think that any of this is coming ever. I could be wrong. But I'm tired of buying locked down Samsung devices because of this. This seems more like a rant but it's more of a psa to developers who wanna help the hopeless. Ya know?
RileyIssKing said:
In case you guys haven't figured it out yet, development, Imo, is dead. There isn't stable root, no rom development outside of slightly modded stuff to change your status bar and the most recent breakthrough was substratum... Which wasn't even meant for this phone but rather the s8 but it still works. Now I use and love substratum but I really want an aosp/pixel rom and stable root and Xposed but I don't think that any of this is coming ever. I could be wrong. But I'm tired of buying locked down Samsung devices because of this. This seems more like a rant but it's more of a psa to developers who wanna help the hopeless. Ya know?
Click to expand...
Click to collapse
I purchased this phone coming from an Iphone 6Plus, thinking I could definitely obtain root on the most sold android phone still in use. Nope. Pretty disappointing as I think it may be the best phone ever made.
RileyIssKing said:
In case you guys haven't figured it out yet, development, Imo, is dead. There isn't stable root, no rom development outside of slightly modded stuff to change your status bar and the most recent breakthrough was substratum... Which wasn't even meant for this phone but rather the s8 but it still works. Now I use and love substratum but I really want an aosp/pixel rom and stable root and Xposed but I don't think that any of this is coming ever. I could be wrong. But I'm tired of buying locked down Samsung devices because of this. This seems more like a rant but it's more of a psa to developers who wanna help the hopeless. Ya know?
Click to expand...
Click to collapse
I didn't do enough research before buying S7. Coming from Nexus 6p this is really foreign to me. I saw s7 had root but didn't look into the 2 different processors, all the different carriers (it doesn't matter on Nexus devices.)
Far as Development goes...its probably not going to happen unless someone finds a way to unlock the bootloader. Next best thing might be Safe Strap but afaik there's nothing in the works.
For now I'm making the best of it. I'm having a decent experience with the Eng kernel. Currently looking into the nonrooted Rom. My hope is I'll be able to make some changes (like installing viper) then switching to the stock boot.img and trying to make those changes stick. Supposedly it's possible but I'm still trying to get some guidance. Experimenting with this phone sucks because the process for root is pretty long then setting everything up THEN it might not work so back to square one.
Especially once done with purchase plan or contract (should you have one) and out of warranty. After that point, it's mine to do with as I please! (I know, should be able to do it whenever, but I'm playing by their rules for a minute.) So it's already BS for those who bought first few months and have paid off.
Personally, what is driving me crazy is battery drain. I'm running about 144k on AnTuTu, so no major complaints with performance, but plugging it in more than once a day sucks. Power drain when I'm not doing anything: sucks. I know it's all this useless crapware running in the background, even tho I killed some with Package Disabler Pro. Just addressing that would improve my mood. If AT&T is trying to ensure we'll all look very carefully at unlocked phones next time, they are doing a bang-up job.

Why is the Verizon S7 Edge root so crappy (serious, not being mean)?

Hey all,
First off let me just say great work to everyone involved with rooting this now "ancient" phone, especially klabit87 and jrkruse. Additionally, I do not mean to be ungrateful with this post, nor suggest that rooting a phone is easy, especially one with a locked bootloader, or that the users here are entitled to such a feature.
With that out of the way....
I haven't looked into rooting this phone EVER until now. Haven't even peaked at XDA or Googled anything, I didn't even know it was possible until yesterday. I've re-ROMed all my previous phones but was actually satisfied with the stock S7 experience other than a Launcher swap and dealing with the always laggy Google maps. Well recently I got a new car and got fed up with the obnoxious list/action limit that Android Auto has as the voice search can be quite unreliable, the letter search is somewhat bugged on the media player I use, and in the end all it does is encourage people to just use their phone to change songs/settings and send messages, thereby completely failing at its goal of being safer. So, I really wanted to get Xposed installed to use the module that makes AA a lot more usable; however, now that I've looked back into the scene a bit, I'm not so sure I want to move forward.
To preface my question: Every Android device I've had before was essentially either rootable or not and ultimately banked on a security exploit that was eventually found. There were never really any concerns about major issues unless you were changing ROMs, kernels, or testing major CPU behavior changes. Just rooting itself was almost always issue free other than a small bug or two or the need to reapply at reboot.
From what I gather, it seems to me that they only way currently to gain root privileges on this device is to install this ENG kernel that's talked about in a lot of more recent posts. Is it truly the case that someone had to write a kernel from scratch that was pre-rooted and as of right now there is no way to root the device as it is stock? Is it that the only known exploit is how to flash another kernel, and the stock kernel is still locked up tight? It sucks that the current root seems so unstable/slow. I know there are a plethora of fixes but there really is no one major fix (other than potentially reflashing the stock bootloader that for some reason seems to work), and its a matter of installing a boat load of CPU and resource management tweaks and even then the performance/battery life isn't quite stock. Additionally it seems like its definitely a YMMV kind of thing as some users seem to still have significant battery drain or slowness/heat even after trying tons of fixes.
Since I am just now getting familiar with the "homebrew" the phone I've had for 3+ years and know nothing about the work that's been done, I genuinely just want to know the technical implications that got in the way of a cleaner root and why the current root method is stuck as sort of a work-around so to speak. The people that manage these breakthroughs rarely post about the process they went through unless its pertinent to a guide on how to root, so I was just curious why the root for this device is in the current state it is.
I would really like to root my Edge so I can be done with the AA nonsense but after just getting a new battery put in I really don't want to go through ****ty battery life again haha.
Thanks to all who weigh in.
Verizon requires most if not all manufacturers to lock the bootloaders. This is also Samsung choice as well. The T-mobile S7/edge and newer have locked bootloaders as well. Difference is T-mobile leaves it up to the OEMs whether they want to lock it or not. With some U.S. businesses and enterprises using Samsung Galaxy devices. They focus on being "enterprise ready" which makes sense from a business standpoint.
Believe it or not, Samsung used to be developer friendly when the S II came out. They even gave away Galaxy S2 devices to some XDA devs.
So, if you want a Samsung device with an unlock able bootloader. Get one that has an Exynos SoC or the Chinese Snapdragon variant.

Categories

Resources