This update brings us up to November security patch.
I assume this is rootable via Odin bootloader swap. Does this update finally enable vulkan?
And how is battery life?
Thanks ahead of time
So far it does seem like it was the stated update to enable 256QAM and 64QAM. But for me only the upload speeds have increased, up to Just over 50Mbps. The speeds in general have been varying from 30Mbps-150Mbps dependent on site, but Just days ago I would be roughly 80Mbps almost everywhere I went, up to about 130Mbps
thowersome said:
I assume this is rootable via Odin bootloader swap. Does this update finally enable vulkan?
And how is battery life?
Thanks ahead of time
Click to expand...
Click to collapse
Vulkans been enabled since the September patch update APIA
I assumed it was but it doesn't seem to be picked up by the apps. For example dolphin emu doesn't pick it up
G930TUVU4APK1_CL9507190_QB11413802_REV02_user_low_ ship_MULTI_CERT.rar
Here are the Odin files:
G930TUVU4APK1_CL9507190_QB11413802_REV02_user_low_ship_MULTI_CERT.rar
After updating to this pdanet force closes about 1 minute after connecting it. Seems there's some new system service that is force closing it. Really low move there tmo
---------- Post added at 10:27 PM ---------- Previous post was at 10:17 PM ----------
If anyone can grab the update files and figure out if there's a new service they introduced maybe I can disable it in package Disabler pro. I really need pdanet to work
Okay now the burning question
... does root work??
KillerClaw321 said:
Okay now the burning question
... does root work??
Click to expand...
Click to collapse
That's what I want to know as I updated and now can't get root access...
CWBPHT said:
That's what I want to know as I updated and now can't get root access...
Click to expand...
Click to collapse
Meaning you flashed the kernel, and used the root.bat but supersu doesnt work?
---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------
esjames said:
This update brings us up to November security patch.
Click to expand...
Click to collapse
Can you root? Or did you try?
KillerClaw321 said:
Meaning you flashed the kernel, and used the root.bat but supersu doesnt work?
---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------
Can you root? Or did you try?
Click to expand...
Click to collapse
I followed the root guide here - http://forum.xda-developers.com/tmobile-galaxy-s7/how-to/root-files-t-mobile-s7-t3488067
I got the boot file flashed and rebooted, but when I run root.bat it just sits there saying waiting-for-device and a security warning pops up on my phone. I have USB debugging enabled and no boot unlock requirement. I had root, then lost it with a previous build and decided to flash stock then update and try again. I'm at my wits end as to what is going on.
Edit - Also, when I type adb devices there are no devices attached, yet I have access to my sd card and phone folders through windows...
CWBPHT said:
I followed the root guide here - http://forum.xda-developers.com/tmobile-galaxy-s7/how-to/root-files-t-mobile-s7-t3488067
I got the boot file flashed and rebooted, but when I run root.bat it just sits there saying waiting-for-device and a security warning pops up on my phone. I have USB debugging enabled and no boot unlock requirement. I had root, then lost it with a previous build and decided to flash stock then update and try again. I'm at my wits end as to what is going on.
Click to expand...
Click to collapse
Then run the cmd as admin
KillerClaw321 said:
Then run the cmd as admin
Click to expand...
Click to collapse
No dice, its still just sitting there and nothing is showing up with adb devices. I've tried switching usb ports, i'm currently trying to reinstall the adb drivers... I'm on windows 7 btw. Is it possible to downgrade the firmware?
CWBPHT said:
No dice, its still just sitting there and nothing is showing up with adb devices. I've tried switching usb ports, i'm currently trying to reinstall the adb drivers... I'm on windows 7 btw. Is it possible to downgrade the firmware?
Click to expand...
Click to collapse
I know it was possible to go from PG1 to PD8, idk about PIA-PG1 or PK1-PG1 ...
KillerClaw321 said:
I know it was possible to go from PG1 to PD8, idk about PIA-PG1 or PK1-PG1 ...
Click to expand...
Click to collapse
I just tried and it wouldn't work through Odin. Getting really frustrated. Something i've read is that the Samsung Galaxy S7 drivers in the Device Manager can interfere with proper ADB functionality. Should I try removing those drivers?
Edit - Just uninstalled the adb drivers and reinstalled using the Android SDK usb drivers and it worked. I've successfully run the root bat, now I'm in a boot loop which I'm trying to fix with another factory reset. We shall see.
CWBPHT said:
I just tried and it wouldn't work through Odin. Getting really frustrated. Something i've read is that the Samsung Galaxy S7 drivers in the Device Manager can interfere with proper ADB functionality. Should I try removing those drivers?
Edit - Just uninstalled the adb drivers and reinstalled using the Android SDK usb drivers and it worked. I've successfully run the root bat, now I'm in a boot loop which I'm trying to fix with another factory reset. We shall see.
Click to expand...
Click to collapse
Oh yes after root you will see a bootloop, but its fine. A factory reset will fixthe issues... just let us know if when you setup the phone you have root.
m52 power! said:
After updating to this pdanet force closes about 1 minute after connecting it. Seems there's some new system service that is force closing it. Really low move there tmo
---------- Post added at 10:27 PM ---------- Previous post was at 10:17 PM ----------
If anyone can grab the update files and figure out if there's a new service they introduced maybe I can disable it in package Disabler pro. I really need pdanet to work
Click to expand...
Click to collapse
If anyone else can confirm that? You could then send a message to the PDANet app team and maybe they'll work in a workaround of some sort.
KillerClaw321 said:
Oh yes after root you will see a bootloop, but its fine. A factory reset will fixthe issues... just let us know if when you setup the phone you have root.
Click to expand...
Click to collapse
Got it up and running and even debloated it, got xposed on there, and I'm working on the tuning guide here - http://forum.xda-developers.com/ver...uide-fine-tuning-performance-battery-t3417804
The only minor annoyance I have as of right now is the phone keeps giving me a "health update" telling me that I have to update Samsung +, but thankfully it stopped giving me the stupid security warnings.
Thanks for the help!
Does this update help with any slowdowns from the Eng Boot root? Even when i set govs to interactive it still lags quite a bit. I'm currently on PG1.
joachim123 said:
Does this update help with any slowdowns from the Eng Boot root? Even when i set govs to interactive it still lags quite a bit. I'm currently on PG1.
Click to expand...
Click to collapse
I've not had any lag problems, but I did optimize a bunch of apps from running in the background, which always helps with battery life.
Related
I have a Ring Plus line that does not have free tethering but I was able to get free WiFi tethering on this Ring Plus line using my Sprint Moto E 2015 XT1526 running 5.1 by doing the following:
1) unlock the bootloader;
2) flash custom recovery twrp-surnia-3.4.5-r1:
http://forum.xda-developers.com/devdb/project/?id=10398#downloads
3) root the device;
4) change the value of "ro.mot.tether_dun_required" to "0" in the build.prop file;
5) add the line "net.tethering.noprovisioning=true" to the end of the build.prop file;
6) in fastboot mode run the following command
Code:
fastboot oem config fsg-id ringplus
7) install MVNO Slayer through TWRP:
http://forum.xda-developers.com/mot...t/flashable-lte-fix-moto-e-6-x-boost-t3290719
Some of the above steps may be unnecessary, idk, but this is what worked for me.
I'm going to try with stock bootloader, loading TWRP through fastboot but leaving stock bootloader, making the build.prop changes and loading the MVNO Slayer. Basically without TWRP and without the fastboot oem config fsg-id ringplus changes. Let's see if it works.
---------- Post added at 02:02 PM ---------- Previous post was at 01:47 PM ----------
mine worked without the config fsg-id ringplus and without the TWRP flash. I just boot into fastboot then type fastboot boot TWRPxxxx.img so it will boot TWRP without loading it permanently.
wpcprez said:
I'm going to try with stock bootloader, loading TWRP through fastboot but leaving stock bootloader, making the build.prop changes and loading the MVNO Slayer. Basically without TWRP and without the fastboot oem config fsg-id ringplus changes. Let's see if it works.
Mine worked without the config fsg-id ringplus and without the TWRP flash. I just boot into fastboot then type fastboot boot TWRPxxxx.img so it will boot TWRP without loading it permanently.
Click to expand...
Click to collapse
So your bootloader is unlocked but you aren't rooted? Or are you rooted?
JulesJam said:
So your bootloader is unlocked but you aren't rooted? Or are you rooted?
Click to expand...
Click to collapse
I think he is trying to avoid root.
Anyway. Kudos to OP. Worked like a charm. Took me a bit of time trying to figure out how to edit build.prop (needed root and build.prop editor from google play). RUSTY OLD ME!
LTE on this Moto E is faster than my daily driver Note 4. wondering if that has anything to do with sim cards......
Is the slayer only for CM Marshmellow? 'cuz it doesn't seem to do anything on my stock 5.1
linhnd2000 said:
I think he is trying to avoid root.
Click to expand...
Click to collapse
But why if you have unlocked the bootloader? Is it due to using the phone for work or something like that?
linhnd2000 said:
Anyway. Kudos to OP. Worked like a charm.
Click to expand...
Click to collapse
Glad it worked for you too!
linhnd2000 said:
Took me a bit of time trying to figure out how to edit build.prop (needed root and build.prop editor from google play). RUSTY OLD ME!
Click to expand...
Click to collapse
I use ES File Manager, but you have to enable the root features on that and I think show hidden files has to be enabled too.
linhnd2000 said:
Is the slayer only for CM Marshmellow? 'cuz it doesn't seem to do anything on my stock 5.1
Click to expand...
Click to collapse
Idk, I just know without it I wasn't able to tether for free on ring plus. I am still on 5.1 so it must have done something to allow me to tether for free.
linhnd2000 said:
I think he is trying to avoid root.
Anyway. Kudos to OP. Worked like a charm. Took me a bit of time trying to figure out how to edit build.prop (needed root and build.prop editor from google play). RUSTY OLD ME!
LTE on this Moto E is faster than my daily driver Note 4. wondering if that has anything to do with sim cards......
Is the slayer only for CM Marshmellow? 'cuz it doesn't seem to do anything on my stock 5.1
Click to expand...
Click to collapse
I'm rooted. I just didn't want to change bootloader to twrp. Heard of people having issues trying to upgrade to newer stock roms when the bootloader is swapped unless you use a custom rom.
All my other devices which are samsung are all rooted,bootloader unlocked and are on TWRP or Philz Touch. All work fine but I just saw others complaining about TWRP And loading stock roms so I thought I would just be safe and just run TWRP from fastboot so I have the features of TWRP without loading it permanently.
Will this work with the Boost Mobile version of this Moto E?
Thanks.
I was able to go through all the steps, with a few hiccups, including accidentally wiping it clean, and I'm able to turn on the hotspot, but a device connected to it can't connect to the internet.
Ended up using the ROM XT1526_Surnia_5_1_1_Lollipop_v1.zip<-For Sprint, Sprint MVNO, and Sprint subsidiaries on XT1526 or XT1529. from this thread
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
unmesh59 said:
Will this work with the Boost Mobile version of this Moto E?
Thanks.
Click to expand...
Click to collapse
Almost sure OP has the boost mobile version as well
SDRebel said:
Almost sure OP has the boost mobile version as well
Click to expand...
Click to collapse
Good to know. I have a new phone waiting in the mailbox for me when I get home
unmesh59 said:
Will this work with the Boost Mobile version of this Moto E?
Thanks.
Click to expand...
Click to collapse
Yes it will, I have done it on both Sprint and Boost.
SDRebel said:
I was able to go through all the steps, with a few hiccups, including accidentally wiping it clean, and I'm able to turn on the hotspot, but a device connected to it can't connect to the internet.
Click to expand...
Click to collapse
Did you check the build.prop file to make sure that your edits were saved and that there weren't any typos in your edits?
JulesJam said:
Did you check the build.prop file to make sure that your edits were saved and that there weren't any typos in your edits?
Click to expand...
Click to collapse
yup, i double-checked it and didn't see any problem. I wonder if the difference could be in the rom, given I had to use the one I linked which may be different than the stock one
Thank you for these instruction. It took me a while to figure out how to each steps, but it works out at the end. I can now have free tethering with my ringplus account. However, my phone camera is no longer accessible. I tried different camera apps, still no go. Is anyone experiencing this? Thanks again
Nurakuni said:
Thank you for these instruction. It took me a while to figure out how to each steps, but it works out at the end. I can now have free tethering with my ringplus account. However, my phone camera is no longer accessible. I tried different camera apps, still no go. Is anyone experiencing this? Thanks again
Click to expand...
Click to collapse
Change SELinux to Permissive. http://forum.xda-developers.com/showthread.php?t=2524485
SDRebel said:
I was able to go through all the steps, with a few hiccups, including accidentally wiping it clean, and I'm able to turn on the hotspot, but a device connected to it can't connect to the internet.
Ended up using the ROM XT1526_Surnia_5_1_1_Lollipop_v1.zip<-For Sprint, Sprint MVNO, and Sprint subsidiaries on XT1526 or XT1529. from this thread
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
Almost sure OP has the boost mobile version as well
Click to expand...
Click to collapse
This process works for BoostMobile Moto E as well. Mine was running Android 5.1 build Number LPI23.29-18-S.2.
However, I decided to experiment to see if I could disable root in SuperSu and the tethering still works. As soon as I disabled root, it stopped working. My PC still connects to the phone, but no Internet access. Damn!
I restored to stock firmware, and had gone through the exact same process again. But it didn't help. My PC can still connect to the phone, bu there is no Internet access. I tried a number of things, same result.
Anyone had the same experience and found a solution?
PhoneHero said:
This process works for BoostMobile Moto E as well. Mine was running Android 5.1 build Number LPI23.29-18-S.2.
However, I decided to experiment to see if I could disable root in SuperSu and the tethering still works. As soon as I disabled root, it stopped working. My PC still connects to the phone, but no Internet access. Damn!
I restored to stock firmware, and had gone through the exact same process again. But it didn't help. My PC can still connect to the phone, bu there is no Internet access. I tried a number of things, same result.
Anyone had the same experience and found a solution?
Click to expand...
Click to collapse
Did you wipe the cache/data partitions? Are you rooted now? What firmware version are you on?
Anyone use on Nexus 5x? (originally from Project Fi)
JeffATL said:
Anyone use on Nexus 5x? (originally from Project Fi)
Click to expand...
Click to collapse
You could try the first 5 steps and see how that works - of course use the proper TWRP for the N5X:
1) unlock the bootloader;
2) flash custom recovery TWRP for your Nexus 5X
3) root the device;
4) change the value of "ro.mot.tether_dun_required" to "0" in the build.prop file;
5) add the line "net.tethering.noprovisioning=true" to the end of the build.prop file
So is this undetectable to boost Mobile? They don't limit you to 8gb like the claim for the hotspot on the $60 unlimited plan ? I have it enabled on my recently purchased moto e and I get extremely fast lte at my rural house. This is awesome and works excellent. Better than the Wi-Fi tether router app I've been stuck using. More reliable with the built-in tether and phone doesn't get nearly as hot.
JulesJam said:
Yes it will, I have done it on both Sprint and Boost.
Click to expand...
Click to collapse
Is this metered tethering or can they not detect this? I'm using Boost unlimited plan $60 and just did this modification and tethering is working great so far, but I just want to know if it's going to stay free like this?
Just now I lost root. My phone working 2 weeks rooted without problem.
SuperSu write me that there is no SU binary installed. I tried with Odin and CF-Auto-Root-hero2lte to root again but the same not root.
Hey me too! Samsung Galaxy S7 Edge
Root was working fine but suddenly lost root, came up with some storage full error, next thing I know, lost root.
Root checker says: Sorry! Root access is not properly installed on this device.
Lemme know if you have any solutions. i'm probably gonna try to backup and then reroot
---------- Post added at 04:57 AM ---------- Previous post was at 04:33 AM ----------
Rerooting with chainfire's AP still shows Root Access is not properly installed. Using Odin3-v3.10.6.exe
---------------------------
Name: CF-Auto-Root-hero2lte-hero2ltexx-smg935f.tar.md5
Size: 87521359 bytes (83 MB)
SHA1: A890B3824A15BEDC35895ECD682B0EDD446636EF
---------------------------
OK
---------------------------
Quote:
Originally Posted by Yanush7
Hi,
I’m writing this to hopefully clarify a little bit the situation about how to get root again on your Samsung device.
The easiest way (which I tasted on my Galaxy S7 Edge), which doesn`t require playing with extraction of boot.img etc., is the following:
1) Check what is your current ROM version
http://forum.xda-developers.com/show....php?t=2772624
2) Download corresponding ROM from - 1GB~~ Download Takes few hours
http://www.sammobile.com/firmwares/
It takes some time for download to complete (sammobile is slow for free users) but it is worth waiting IMO.
Tip: when you find your ROM there, you can copy the full filename and try to google it for some mirror links, just be smart and do not download from some trash sites.
3) Download newest Odin 3.11
http://forum.xda-developers.com/atta...1&d=1463117260
4) Download updated CF Auto Root (all the files now are already updated by Chainfire, and it will protect you from losing root again)
https://autoroot.chainfire.eu/
5) Using Odin, flash your ROM (which you just downloaded) to your device. I won`t describe whole process, as there is many tutorials. But in general, after putting your phone in Download Mode, and connecting to PC, you run Odin, and you select only the AP file (you can ignore the other files in package with names that starts from CSC, BT, Home_CSC etc.)
You will not lose any data. This is important. If you download ROM which match the ROM you already have on your phone, then you can flash the entire ROM without losing any data, settings etc.
6) After flashing your ROM, now you can flash CF Auto Root and root your phone like you did once before.
I tested it on my phone and everything worked without problem.
pd56 said:
Just now I lost root. My phone working 2 weeks rooted without problem.
SuperSu write me that there is no SU binary installed. I tried with Odin and CF-Auto-Root-hero2lte to root again but the same not root.
Click to expand...
Click to collapse
Haha me too! The last thing I remember doing is unfreezing the edge screen functions and logging into that "oncircle" or whatever thing. Because I've never known what it is! And the next thing I know, TB doesn't have too. I had it minutes ago. Then I reflashed SuperSU from TWRP and its back to normal. And froze that useless edge screen nonsense.
---------- Post added at 09:55 AM ---------- Previous post was at 09:54 AM ----------
IVPathfinder said:
Hey me too! Samsung Galaxy S7
Root was working fine but suddenly lost root, came up with some storage full error, next thing I know, lost root.
Root checker says: Sorry! Root access is not properly installed on this device.
Lemme know if you have any solutions. i'm probably gonna try to backup and then reroot
---------- Post added at 04:57 AM ---------- Previous post was at 04:33 AM ----------
Rerooting with chainfire's AP still shows Root Access is not properly installed. Using Odin3-v3.10.6.exe
---------------------------
Name: CF-Auto-Root-hero2lte-hero2ltexx-smg935f.tar.md5
Size: 87521359 bytes (83 MB)
SHA1: A890B3824A15BEDC35895ECD682B0EDD446636EF
---------------------------
OK
---------------------------
Click to expand...
Click to collapse
Do you not have TWRP?
thedisturbedone said:
Haha me too! The last thing I remember doing is unfreezing the edge screen functions and logging into that "oncircle" or whatever thing. Because I've never known what it is! And the next thing I know, TB doesn't have too. I had it minutes ago. Then I reflashed SuperSU from TWRP and its back to normal. And froze that useless edge screen nonsense.
---------- Post added at 09:55 AM ---------- Previous post was at 09:54 AM ----------
Do you not have TWRP?
Click to expand...
Click to collapse
In the beginning when i lost root i had after not. I flashed again and restore inside from TWRP older back up. First reboot looks that I have root. I hope to stay like that.
Nop again I lost root without to do anything.
pd56 said:
Nop again I lost root without to do anything.
Click to expand...
Click to collapse
Do a Full wipe, reroot and your problems will be gone.
pd56 said:
Nop again I lost root without to do anything.
Click to expand...
Click to collapse
Oh sorry to hear that! I have mine intact so far. I don't know what exactly caused it..but I had a random reboot today!
We must wait for updates superSu or TW. I made clean stock firmware flash and after one hour had the same, no root
Tiny Wiz said:
Do a Full wipe, reroot and your problems will be gone.
Click to expand...
Click to collapse
If i do a full wipe, will i lose all my installed programs and have to reinstall everything again?
Edit: Only asking because i also lost root after installing the latest Australian Optus firmware so i went back to older firmware.
krico said:
If i do a full wipe, will i lose all my installed programs and have to reinstall everything again?
Edit: Only asking because i also lost root after installing the latest Australian Optus firmware so i went back to older firmware.
Click to expand...
Click to collapse
Yes you need to reinstall all your programs and don't forget to take backup of data (pictures, videos, documents, music).
At the same time you will remove the "bug" that is causing the removal of root.
Normally root don't disapear for no reason unless there is a bug in SuperSU, or you have installed a program that you might or might not know removes root.
If there was such a bug in SuperSU that removes itself then there would be a widespread reaction among other users and an update would have been released.
So try it out, and please report back so others with similar problem can see if it was success or not.
I also lost root today...
My guess is I saw an OTA security update(google android) going on today and after some time(it has been installed) I realised I lost root.
Weird is that I am on a custom ROM TEKXnesis HYBRID S7E URv4.5
I thought that being on a custom ROM I will not get OTA updates anymore ?!
Tiny Wiz said:
Yes you need to reinstall all your programs and don't forget to take backup of data (pictures, videos, documents, music).
At the same time you will remove the "bug" that is causing the removal of root.
Normally root don't disapear for no reason unless there is a bug in SuperSU, or you have installed a program that you might or might not know removes root.
If there was such a bug in SuperSU that removes itself then there would be a widespread reaction among other users and an update would have been released.
So try it out, and please report back so others with similar problem can see if it was success or not.
Click to expand...
Click to collapse
Yesterday I got an safety guideline update. Maybe this cause problems on your rooted phones? As I read this happened out of no where, so maybe it's caused from this update.
Sent from my SM-G935F using XDA-Developers mobile app
Tiny Wiz said:
If there was such a bug in SuperSU that removes itself then there would be a widespread reaction among other users and an update would have been released.
Click to expand...
Click to collapse
Bug or no bug (and I hope it is the former), there already is a widespread reaction. I lost root out of the blue - 935FD rooted with CF auto root method, no TWRP, Xposed installed using FlashFire, stock ROM. The last update I recall was to an Xposed module called "Flat Style Bar Indicators" - which is totally awesome and works very well.
I don't think I want to go the TWRP route, wipe everything and start from scratch, only to lose root again.
Fingers crossed for it to be an SU bug and simply fixed by flashing an updated version via ODIN.
And now that I've lost root, will I be able to get and install OTA update when one for my region becomes available?
i lost my phone , but not the root
I lost root randomly as well on my Galaxy S7 G930F. I rooted the phone about a month ago and had no issues at all. This just appeared randomly out out of the blue. I'm thinking it might have been some sort of OTA security update pushed to my phone as some others mentioned, but I can't be sure. I tried re-rooting with CF-Autoroot, but SuperSU still says I'm not rooted. Will an update to CF-Autoroot or SuperSU fix this? I would prefer not to start from scratch.
I had the same problem and stop Security Aytomatic updates. Looks than 12 hours now and still I have the root. Hope to stay like that
Yep same here, I mentioned this a few days ago. I went with CF Auto Root and flashed zips with FlashFire. I did get a warning about a security policy update around the same time. I think I picked the install later option. Lost root in the end though. I went with the nuclear option
Flashed stock image, updated to latest UK OTA. Flashed TWRP, didn't full wipe after setting up (I don't need /data to be accessed, I just flash zip from external SD). So I still have encryption. Didn't flash dm verity (don't need to). Back to normal now. I've rebooted multiple times and haven't lost root yet. I've disabled automatic security updates too.
Same happened to me, I receiced a security update notification, and then, in titanium back up I realize I lost root, fortunately I was able to reboot in TWRP with button combo and flashed supersu.zip to gain root again, but I'm curios how this happened and what backdoor this security update use to unroot
Sent from my SM-G935F using XDA-Developers mobile app
Hey WTF. I have also a Galaxy S7 Edge SMG935F and about one week ago I had root with no problems. Today I wanted to use root again and my TB tells me no root. So i download root checker and it also tells me no root. So I rerooted my Samsung with CF-Auto-Root-hero2lte-hero2ltexx-smg935f and then tried again and still I have no root. I have not done any updates. So what the hack has happened. I don't want to wipe my Samsung just to find out it might not work or I will lose root again. Can someone please help me or tell me what happened. Thanks.
---------- Post added at 08:25 PM ---------- Previous post was at 08:07 PM ----------
stremax said:
Same happened to me, I receiced a security update notification, and then, in titanium back up I realize I lost root, fortunately I was able to reboot in TWRP with button combo and flashed supersu.zip to gain root again, but I'm curios how this happened and what backdoor this security update use to unroot
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Hey can I flash a custom recovery without root to be able to use the supersu.zip to gain root again?
chrisdzie said:
Hey WTF. I have also a Galaxy S7 Edge SMG935F and about one week ago I had root with no problems. Today I wanted to use root again and my TB tells me no root. So i download root checker and it also tells me no root. So I rerooted my Samsung with CF-Auto-Root-hero2lte-hero2ltexx-smg935f and then tried again and still I have no root. I have not done any updates. So what the hack has happened. I don't want to wipe my Samsung just to find out it might not work or I will lose root again. Can someone please help me or tell me what happened. Thanks.
---------- Post added at 08:25 PM ---------- Previous post was at 08:07 PM ----------
Hey can I flash a custom recovery without root to be able to use the supersu.zip to gain root again?
Click to expand...
Click to collapse
Just follow the TWRP install steps. You have to full wipe if you don't have an external SD card to flash mods unless you want to disable encryption............which I don't think is a smart idea.
https://plus.google.com/communities/105935130933812628608
Check your System update center
Officially downloading at 11 PM but I changed my time to 11:30 and it is installing now
Marshmallow
I'm on katana rom, could someone help me with steps to update to MM? I would also like help with root and Xposed installation for MM. Thanks in advance.
Im having an issue updating. i tried it once and upon restarting my phone it was updating just fine and then it just said error. then it restarted and now i'm not receiving the OTA update.
Mrtubby said:
Im having an issue updating. i tried it once and upon restarting my phone it was updating just fine and then it just said error. then it restarted and now i'm not receiving the OTA update.
Click to expand...
Click to collapse
Hello. Are you rooted? Or with twrp? Go back to stock recovery and unroot, the update checks for moddified system and aborts the install. Once you go back to stock. Recovery and unrooted you have to go to settings. Apps. All apps. Look for google services and manage space and clear data. Then look for google services framework and clear data and cache and force close. Then check again for update and shoulsld start downloading it.
---------- Post added at 02:05 AM ---------- Previous post was at 01:47 AM ----------
Mrtubby said:
Im having an issue updating. i tried it once and upon restarting my phone it was updating just fine and then it just said error. then it restarted and now i'm not receiving the OTA update.
Click to expand...
Click to collapse
Checking on what i said previously. It wont update after unrooting with super su. Have to get back to full stock... We have to wait for somebody that make a twrp flashable 6.0 update. Or a metro pcs go-back-to-stock procedure...
danielpsx said:
Hello. Are you rooted? Or with twrp? Go back to stock recovery and unroot, the update checks for moddified system and aborts the install. Once you go back to stock. Recovery and unrooted you have to go to settings. Apps. All apps. Look for google services and manage space and clear data. Then look for google services framework and clear data and cache and force close. Then check again for update and shoulsld start downloading it.
---------- Post added at 02:05 AM ---------- Previous post was at 01:47 AM ----------
Checking on what i said previously. It wont update after unrooting with super su. Have to get back to full stock... We have to wait for somebody that make a twrp flashable 6.0 update. Or a metro pcs go-back-to-stock procedure...
Click to expand...
Click to collapse
did you try lg bridge?
bigjay1114 said:
I'm on katana rom, could someone help me with steps to update to MM? I would also like help with root and Xposed installation for MM. Thanks in advance.
Click to expand...
Click to collapse
I'm also on katana. I'm not sure if it's okay to just update straight from the OTA or not. I'm probably not going to update until someone releases a root and xposed method. Can someone more experienced confirm/deny the safety of accepting official OTA while on a custom ROM?
redacted187 said:
I'm also on katana. I'm not sure if it's okay to just update straight from the OTA or not. I'm probably not going to update until someone releases a root and xposed method. Can someone more experienced confirm/deny the safety of accepting official OTA while on a custom ROM?
Click to expand...
Click to collapse
No.
You can never install an OTA on a rooted phone. Never ever. It will bork your phone.
If you really want the OTA, go back to stock via kdz and then proceed.
If you are not rooted and get the OTA, after install, it will ask to update google play services. You may see some error messages as it needs to update apps. to MM.
noobiedev83 said:
did you try lg bridge?
Click to expand...
Click to collapse
Hi. I just downloaded the kdz file. Im going to flash the kdz file to put it stock and then update to mm. I did not tried other procedure but on every forum people says "thou shall not install an ota on a rooted phone" so im sticking to those words right now... Ill be back with results... But maybe tomorrow, i gotta go to work.
Don't Bother...
While Marshmallow on the LG Gstylo sports some really cool features the battery life suck donkey nuts. I reverted back to the Kitana roms just because of that. Not much else to say... Hopefully a new update will come from the Marshmallow to improve battery life.
I just received the update too but if the battery sucks and no xposed then I don't see a really good reason to go to all the trouble I'll just stay in my katana until something better comes along
danielpsx said:
Hello. Are you rooted? Or with twrp? Go back to stock recovery and unroot, the update checks for moddified system and aborts the install. Once you go back to stock. Recovery and unrooted you have to go to settings. Apps. All apps. Look for google services and manage space and clear data. Then look for google services framework and clear data and cache and force close. Then check again for update and shoulsld start downloading it.
Click to expand...
Click to collapse
I just made this account about thirty seconds ago. I mostly lurk for minor things, so sorry if I don't seem totally sure of what's up. I've seen a few of your posts and you're here now so I might as well ask.
I'm having this issue as well. I followed a guide here on how to root so I could remove ads and use some apps. I updated without thinking this morning which leading to an error - no clue what kind - and I promptly undid the root and I'm still not having any luck. After clearing the cache and like I can get the device to recognize it needs an update, but it keeps getting an error during the actual update and we're back at square one. I've tried LG Bridge and LG Bridge thinks my device is up to date.
I tried looking for some guides on how to get this to work, but I keep reading that I'll lose OTA for future updates. I also don't even know where to start on the fixes I've read since they jump head-first into stuff I've never seen or know where to read about before.
Click to expand...
Click to collapse
RicanBoy said:
While Marshmallow on the LG Gstylo sports some really cool features the battery life suck donkey nuts. I reverted back to the Kitana roms just because of that. Not much else to say... Hopefully a new update will come from the Marshmallow to improve battery life.
Click to expand...
Click to collapse
Clear your cache partition and reboot your phone.
Make sure all apps are updated.
If that fails you need to do a factory data reset.
Battery life is just fine on my wife's Stylo. I've had MM using the T-mobile version on my Metro Stylo. Battery life is fine.
Does anyone know how long it'll take for a flashable zip of android 6.0 to show up
noobiedev83 said:
did you try lg bridge?
Click to expand...
Click to collapse
yeah dude i tried but while updating it stops and says error.
i just followed this guide, it works real good.
http://forum.xda-developers.com/lg-g-stylo/how-to/failproof-method-unroot-return-to-stock-t3378954
---------- Post added 16th May 2016 at 12:20 AM ---------- Previous post was 15th May 2016 at 11:55 PM ----------
Whassamattau said:
I just made this account about thirty seconds ago. I mostly lurk for minor things, so sorry if I don't seem totally sure of what's up. I've seen a few of your posts and you're here now so I might as well ask.
I'm having this issue as well. I followed a guide here on how to root so I could remove ads and use some apps. I updated without thinking this morning which leading to an error - no clue what kind - and I promptly undid the root and I'm still not having any luck. After clearing the cache and like I can get the device to recognize it needs an update, but it keeps getting an error during the actual update and we're back at square one. I've tried LG Bridge and LG Bridge thinks my device is up to date.
I tried looking for some guides on how to get this to work, but I keep reading that I'll lose OTA for future updates. I also don't even know where to start on the fixes I've read since they jump head-first into stuff I've never seen or know where to read about before.
Click to expand...
Click to collapse
hey, i did that too. got the update notification, downloaded the update and reboot to update. i was rooted and had twrp. so the first error was the reboot to twrp and no update, booted the phone, reverted to stock recovery with flashify (thanks god ive made a recovery backup) tried the update, this time i got to see the green android update screen but got error stopped the update, boot the phone unrooted, downloaded the update again and same error. so ive lurked the interwebs and no luck....
then i saw this post.
http://forum.xda-developers.com/lg-g-stylo/how-to/failproof-method-unroot-return-to-stock-t3378954
i followed, and now have android 6.0
Click to expand...
Click to collapse
Everyone knows that RRO/layers is baked in to all marshmallow ROMS, right? All you have to do is root, then install layers manager from playstore. That's why I want the update. I'm so surprised nobody talks about this.
mustangtim49 said:
Everyone knows that RRO/layers is baked in to all marshmallow ROMS, right? All you have to do is root, then install layers manager from playstore. That's why I want the update. I'm so surprised nobody talks about this.
Click to expand...
Click to collapse
oh really? i just kdz'd back to stock...waiting to get the update, root it and give that a try :good:
mustangtim49 said:
Everyone knows that RRO/layers is baked in to all marshmallow ROMS, right? All you have to do is root, then install layers manager from playstore. That's why I want the update. I'm so surprised nobody talks about this.
Click to expand...
Click to collapse
Please elaborate....
Goongydin said:
Please elaborate....
Click to expand...
Click to collapse
Sorry I haven't been around, I know it sucks I left everyone hanging on that bit of information. Yes, Google has baked RRO/layers into marshmallow. Just like I said before, all you need is root, then layers manager app from the play store. Sometimes it takes like 2 or 3 tries to get it to work, but, being a fan of theme chooser since Cm7, I love the ability to theme everything, I love making everything dark and transparent. So, I just haven't had the time to return to stock and update, but has anyone else tried what I said?
Update!!!! Ive got some layers to apply. Please excuse my signature as i dont work for android headlines anymore. Well, that should cause all kinds of buzz around these forums.
New update! Apparently I over shot the Android version, RRO layers is in lollipop also
I applied the wrong ota file by mistake and now the phone is stuck in bootloop.
phone is unlocked and "fastboot flashing unlock" won't work as unlocking was disabled in developer options.
Factory reset didn't work. Further, getting the Google's device corrupted message during the bootloop.
Any solutions?
sumit29 said:
I applied the wrong ota file by mistake and now the phone is stuck in bootloop.
phone is unlocked and "fastboot flashing unlock" won't work as unlocking was disabled in developer options.
Factory reset didn't work. Further, getting the Google's device corrupted message during the bootloop.
Any solutions?
Click to expand...
Click to collapse
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Is it possible to downgrade to an older OTA? I received DP3, got a bootloop. Tried sideloading, wiping, nothing solved.
I´m trying to sideload DP2 but it gives me this error:
Cant install this package over newer build
E: error in /sideload/package.zip (Status 7)
gasparzim said:
Is it possible to downgrade to an older OTA? I received DP3, got a bootloop. Tried sideloading, wiping, nothing solved.
I´m trying to sideload DP2 but it gives me this error:
Cant install this package over newer build
E: error in /sideload/package.zip (Status 7)
Click to expand...
Click to collapse
No, as per the instructions in my guide you can only install a newer build. I wasn't aware that full OTA zips were even available for the Developer Previews.
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Have already tried doing this...this also gets interrupted mid-way, with the command terminal showing - "connection reset by peer". these are the same OTA files available on the google developers website.
and for some reason, it worked this time around!!!
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Ame123 said:
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Click to expand...
Click to collapse
Same problem have you been able to sort it out yet?
Ame123 said:
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Click to expand...
Click to collapse
AlfexOmega said:
Same problem have you been able to sort it out yet?
Click to expand...
Click to collapse
I don't know what you can do, sorry. I'm not sure why you wouldn't just unlock your bootloader and leave it unlocked, that alone would mean you could fix this issue in a matter of minutes. I know me saying this is of no use to you right now, but hopefully it'll impress on you (and anyone reading) the importance of having a fail-safe when things go sideways like this.
Heisenberg said:
I don't know what you can do, sorry. I'm not sure why you wouldn't just unlock your bootloader and leave it unlocked, that alone would mean you could fix this issue in a matter of minutes. I know me saying this is of no use to you right now, but hopefully it'll impress on you (and anyone reading) the importance of having a fail-safe when things go sideways like this.
Click to expand...
Click to collapse
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
AlfexOmega said:
Same problem have you been able to sort it out yet?
Click to expand...
Click to collapse
no.:crying::crying:
Ame123 said:
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
no.:crying::crying:
Click to expand...
Click to collapse
An update failing is the single most likely cause of a problem like this. The issue here isn't with the update itself, otherwise pretty much every other user taking the update would be experiencing the same thing. There could be any number of reasons for this update going badly for you.
If you had researched you would have known that you need to unlock the bootloader when you first get the device, before you commit too much data to it. Either that or just back up your personal data, unlock the bootloader and then copy your data back. Surely even that is a better option that being stuck in a situation like this where you essentially have a brick.
All you can do now is contact Google support, explain what has happened, and ship it off to them to have it fixed. You shouldn't have to pay if it genuinely wasn't your fault. And remember to unlock your bootloader when you get it back.
Heisenberg said:
An update failing is the single most likely cause of a problem like this. The issue here isn't with the update itself, otherwise pretty much every other user taking the update would be experiencing the same thing. There could be any number of reasons for this update going badly for you.
If you had researched you would have known that you need to unlock the bootloader when you first get the device, before you commit too much data to it. Either that or just back up your personal data, unlock the bootloader and then copy your data back. Surely even that is a better option that being stuck in a situation like this where you essentially have a brick.
All you can do now is contact Google support, explain what has happened, and ship it off to them to have it fixed. You shouldn't have to pay if it genuinely wasn't your fault. And remember to unlock your bootloader when you get it back.
Click to expand...
Click to collapse
the place where i stay does not have any support so that i can ship to them. i bought the device from uk but now i stay in UAE. I dont know what to do now:crying::crying: . Also there are many such cases on xda having the same issue.
Ame123 said:
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
no.:crying::crying:
Click to expand...
Click to collapse
Mine is also still messed up I'm calling the store where I bought it to see if they can do anything highly doubt they will though
Ame123 said:
the place where i stay does not have any support so that i can ship to them. i bought the device from uk but now i stay in UAE. I dont know what to do now:crying::crying: . Also there are many such cases on xda having the same issue.
Click to expand...
Click to collapse
Oh, that is not a good situation at all. You might need to find a good repairer in your area and pay for them to fix it for you.
Heisenberg said:
Oh, that is not a good situation at all. You might need to find a good repairer in your area and pay for them to fix it for you.
Click to expand...
Click to collapse
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
AlfexOmega said:
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
Click to expand...
Click to collapse
An accredited repair centre should have access to software tools that can do it.
AlfexOmega said:
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
Click to expand...
Click to collapse
ADB Sideload the developer 3 preview 3 like the other user successfully did.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
ADB Sideload the developer 3 preview 3 like the other user successfully did.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
did not understood what you said. can you explain a little bit more?
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Ame123 said:
did not understood what you said. can you explain a little bit more?
Click to expand...
Click to collapse
Sure, see the above post.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Sure, see the above post.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've tried sideloading multiple times and they succeeded however my phone is still not booting :/
Hey fellas,
I have been looking around on some threads here and there and decided to change my phone to G935U to get off the Verizon one. I took an update that I probably shouldnt have and it brought me to the API3, can this be rooted? I tried following the known root method (and pretty much the only one I can find) and it doesn't seem to work.
I havent seen anybody else say API3 is unrootable so I figure I would ask.
No root for it yet. Not sure if there ever will be. The current root method for earlier versions is somewhat unreliable and tends to slow your system down and drain the battery so I'm not even sure what the demand would be.
Rooted pi3 checking in. Stock rooted, debloated, running smooth. Kernel auditor is basically a must. I run amplify, greenify, force dose, lean Droid and L speed. The fixes and vvm zip change the csc and what not to g935V and make it say I'm on peh. Runs better than any custom room I've ran, but debloating it to my liking did take some time. In short yes you can root it. You can even manually flash updated supersu binaries through flash fire but you will have to replace the engboot immediately after or your device won't boot.
ShadowyStorm said:
Rooted pi3 checking in. Stock rooted, debloated, running smooth. Kernel auditor is basically a must. I run amplify, greenify, force dose, lean Droid and L speed. The fixes and vvm zip change the csc and what not to g935V and make it say I'm on peh. Runs better than any custom room I've ran, but debloating it to my liking did take some time. In short yes you can root it. You can even manually flash updated supersu binaries through flash fire but you will have to replace the engboot immediately after or your device won't boot.
Click to expand...
Click to collapse
Do you have a link on how to do all this?
Replied to your pm. Regular root method works just fine though. So Lmk what issues you're having.
ShadowyStorm said:
Rooted pi3 checking in. Stock rooted, debloated, running smooth. Kernel auditor is basically a must. I run amplify, greenify, force dose, lean Droid and L speed. The fixes and vvm zip change the csc and what not to g935V and make it say I'm on peh. Runs better than any custom room I've ran, but debloating it to my liking did take some time. In short yes you can root it. You can even manually flash updated supersu binaries through flash fire but you will have to replace the engboot immediately after or your device won't boot.
Click to expand...
Click to collapse
Checking in also-- very similar to yours.
Bought the phone with PI3 already installed. Flashed the U firmware, debloated (only a few really) and rooted. I also use Kernel Auditor set to ondemand (<--must) and L speed. Flashed the two Verizon fixes with flashfire and working great. The phone was laggy and would randomly freeze for 10 seconds or so before I downloaded Kernel Auditor, but that along with .5s animations really makes things snappy.
Knox status - 0x0 - not tripped
Samsung Pay doesn't work, but I just tested Android Pay and it does work!
Snapchat works if installed and run once before rooting. Rooted now and still working.
Xposed installed through Flashfire.
The only thing I haven't had a chance to test yet is VR, but I see no reason why it wouldn't.
I am on PI3 rooted running smoothly. Also did my friends phone the same way. If you are having issues rooting there is a workaround that i discovered which worked for me and my friend because both of use after flashing to PI3 wouldnt root successfully. The workaround is using the Verizon Repair Assitant and "repairing the phone" this will put a new 935u IMAGE from verizon onto your phone and it will reboot. I dont know what the difference is between this image they put on your phone and the one we did but there is a difference. I say this becuase after you do that if you run through the root process again by flashing then installing su over ADB it works flawlessly. PM if you need further help.
I still cant get it to root... Tried it several times, zero luck
What Odin are you using?
ShadowyStorm said:
What Odin are you using?
Click to expand...
Click to collapse
The PrinceComsy one. I have debugging and unknown sources enaqbled. I run the root.bat and nothing happens, it sits at
"adb push SuperSU-v2.76.img /data/su.img"
like it just hangs indefinitely? try a different cord. it doesnt say its retarting the server a million times?
Did you flash the Eng Hboot kernel in the AP slot first? more info needed
ShadowyStorm said:
like it just hangs indefinitely? try a different cord. it doesnt say its retarting the server a million times?
Did you flash the Eng Hboot kernel in the AP slot first? more info needed
Click to expand...
Click to collapse
Pretty much indefinitely. I let it sit an hour and nothing. I transferred about 200gb of audio to the phone with zero issues so I think the cable is fine (but I tried a new one anyway, nothing). It never says restating the server.
Yes I flashed the engineer kernel in the ap slot first.
What other information can I provide?
Did you install the adb drivers in the root thread?
ShadowyStorm said:
Did you install the adb drivers in the root thread?
Click to expand...
Click to collapse
Yes
Hell-Razor said:
Yes
Click to expand...
Click to collapse
Well ****. Try turning off USB debugging and turn it back on again maybe for reason your phone blocked the connection and this would renew that list
ShadowyStorm said:
Well ****. Try turning off USB debugging and turn it back on again maybe for reason your phone blocked the connection and this would renew that list
Click to expand...
Click to collapse
Give me about two minutes and Ill get right back toyou
Aaaand nothing
My phone reboots, supersu is on it but root is not there.
Hell-Razor said:
My phone reboots, supersu is on it but root is not there.
Click to expand...
Click to collapse
Try another USB port on your computer maybe...
If that doesn't work then try opening up a command prompt as administrator on your computer (I know you've tried running root.bat as admin but windows has its quirks) and navigating through the directories until you're in the folder with the root.bat file and type in root.bat once you're there to see if that changes anything. If you need help with commands in the command prompt then ask. I'll gladly help.
That's interesting. It sounds like it's not able to mount the system as writable.
---------- Post added at 08:31 PM ---------- Previous post was at 08:15 PM ----------
http://forum.xda-developers.com/ver...de-flashing-sm-935u-firmware-verizon-t3415145 root files from this thread right? Try re downloading all of it and then flash the rooted tar as ap and then get back to me on the results
---------- Post added at 09:24 PM ---------- Previous post was at 08:31 PM ----------
So I was able to replicate this scenario... I had to restart my computer because the adb server kept going out of date due to Odin being open as well as trying to root the phone. Restarting restored proper communication. Try using smart switch to install your phone drivers