Related
So.. if I missed any posts dealing with this, please forgive me. I am a total noobie at this hobby so I'm not really familiar with all the acronyms or terminology thrown around. I have an M8 HK, I rooted the phone using Opensourcegangster's youtube video. I was able to wi-fi tether no problem. All was good for a few days until the 1.54.654.13 update tried to come through. OK, so the rooted phone wouldn't update the phone, because of the root? I understand that and it kept asking to update. I didn't have time to do update the phone and it asked every 2 hours for days, Now, the phone has stopped asking to update but has also started dropping every call after 10 sec even though signal strenghth seems to be strong and now won't connect to 3G or LTE data. I don't know if any of this is related or if I can even go to a store for help because of the root.
Thanks in advance
chinrednek said:
So.. if I missed any posts dealing with this, please forgive me. I am a total noobie at this hobby so I'm not really familiar with all the acronyms or terminology thrown around. I have an M8 HK, I rooted the phone using Opensourcegangster's youtube video. I was able to wi-fi tether no problem. All was good for a few days until the 1.54.654.13 update tried to come through. OK, so the rooted phone wouldn't update the phone, because of the root? I understand that and it kept asking to update. I didn't have time to do update the phone and it asked every 2 hours for days, Now, the phone has stopped asking to update but has also started dropping every call after 10 sec even though signal strenghth seems to be strong and now won't connect to 3G or LTE data. I don't know if any of this is related or if I can even go to a store for help because of the root.
Thanks in advance
Click to expand...
Click to collapse
In order to accept an OTA update, such as the one trying to come through on your phone, you need to have stockish Sense Rom and the Stock Recovery. I haven't seen the video you mentioned but if your method of rooting involved installing a custom recovery this is likely why your update is failing. Your phone will reboot, enter your custom recovery, attempt to run the script, fail, rinse and repeat until you revert to stock recovery. Lucky for you rooting is really easy to undo, all you need to do is grab the stock recovery for your HK (I pulled the one out of the .9 RUU that's up at another link, i'll try to post it for you in a minute), and then reboot to fastboot (this requires the android SDK and administrator level command window - shift+right click the folder fastboot.exe is in and select open command window here). Then to flash it type "/fastboot flash recovery recovery.img" with no quotes and make sure you have the recovery in the same folder as fastboot. Give me a few minutes here and ill give you the recovery.img file you need.
Here is the link for the M8 HK stock recovery: http://rg.to/file/8e32e8cc37ac93d3f0206994f1c7a59b/recovery.img.html
That should be all you need to either a) accept the OTA (there are other methods of getting this update since you're rooted btw) or b) visit a sprint store and have them check over your phone.
As I suffered data loss on my first HK and no matter what could not fix it I suggest going with the lengthier method of getting the update as I've listed it above so that you can go in and get your phone checked out.
Oh, the bootloader.... so there is another step to take if you want to appear 100% unmodified and this step should be completed before you unroot...
I followed this method and had a Sprint technician run tests on my phone later that day and had 0 issues getting a replacement device...
It's a bit much to go into so I'm just going to link you to the forum page I followed: http://forum.xda-developers.com/showthread.php?t=2710503
You will need to grab the "Faux Locked Hboot" for Sprint near the bottom of the first post and then follow the instructions listed prior to it in the top section.
EDIT: It just occurred to me that you are S-ON, yes? The phone I did this with was S-OFF so I'm not 100% certain it will work for you. Can anyone else confirm that you can flash a modified Hboot in rebootRUU state being S-ON? Or perhaps have another method of making the bootloader say Locked and not Relocked as "/fastboot oem lock" results in?
It is about time I get some straight-forward answers. I'm tired of Googling everything I can and it not being what I think it is.
It is about time I get some straight-forward answers. I'm tired of Googling everything I can and it not being what I think it is.
What I have come to you for, XDA, is some light in the cave.
WILL THERE BE A WAY TO ROOT THE AT&T SAMSUNG GALAXY S5 VARIANT?!
Towelroot doesn't work. And if quite frankly tired ****less of all the posts that still exist talking about it.
Is there anything in development? All I can see now is SafeStrap and Multi-Tool but if you aren't rooted these do nothing. I just want some information for God's sake. Will ANYONE tell me what is being done about the development of the device's rooting? Is anyone even trying anymore? And if so, tell me! More importantly, if there are people, why aren't they being talked about? With as many S5's as there are out there (at least to me since I know about 10 people who use them regularly) why wouldn't anyone be trying?
PLEASE people get it together!
I have come from only 3 devices, but I was able to root and mod all of them. Rooting and Modding is love and life to me and is pretty much all I sincerely love about Android. The fact that I can't afford a new phone at this stage is sad, and I have grown tired of the bloating of TouchWiz, especially with the Lollipop update. I know that a rooted S5 would be extremely awesome, but since there is nothing about it being worked on I suppose I'll just have to live with the rubbish they call TouchWiz.
And if by some chance someone who can develop something like this reads this thread, please, respond, PM me, do SOMETHING. TELL THE XDA WORLD, because I GUARANTEE there are more of me out there who have longed for this but have just lived with it. BE A GAME CHANGER A DO SOMETHING ABOUT IT.
Don't give me the, "Knox and bootloaders are hard to pass by, especially with the new more secure versions." Because guess what, geohot did it once. Not like it lasted, but the fact is is that it worked at one point. It may be harder now, but it's still possible. PLEASE DO SOMETHING. PLEASE TRY.
Anyway, best of luck to all of the users. And anyone who has read this please leave a comment and tell me what you know. Many days I'm left alone, commentless with my threads. This is one I truly need to be acknowledged.
THANK YOU FOR YOUR TIME
Well that's a big thread revealing nothing about your device other than its an s5. There are ways to root with towel root unless you have the 5.0 ota.
dirtydodge said:
Well that's a big thread revealing nothing about your device other than its an s5. There are ways to root with towel root unless you have the 5.0 ota.
Click to expand...
Click to collapse
Well it's pretty obvious that it's AT&T. 5.0 L and Towelroot has never worked before.
ElectricBiskitz said:
Well it's pretty obvious that it's AT&T. 5.0 L and Towelroot has never worked before.
Click to expand...
Click to collapse
Towel root has worked and still does on nce. If you were on OA1 towel root wouldn't work unless you downgraded to use it then go back to OA1. And no it don't work on 5.0. There are multiple kernels and builds that att has put out that it didn't work on without downgrading. But just for future reference is always helpful if you include your build, version, etc. Like i said there are multiple builds that it didn't work on unless you downgraded is only the 5.0 that you can't downgrade.
dirtydodge said:
Towel root has worked and still does on nce. If you were on OA1 towel root wouldn't work unless you downgraded to use it then go back to OA1. And no it don't work on 5.0. There are multiple kernels and builds that att has put out that it didn't work on without downgrading. But just for future reference is always helpful if you include your build, version, etc. Like i said there are multiple builds that it didn't work on unless you downgraded is only the 5.0 that you can't downgrade.
Click to expand...
Click to collapse
I said that I have Lollipop so everything you're saying won't help. Plus I know you wouldn't have known anyway but I have tried all of this way before Lollipop. I tried downgrading from OA1 at the time to NCE and I ended up in a bootloop. The kernel was faulty. I had to reset my phone in a very long, aggravating process to get it back. I NEVER want to go down that road again. And like I said in the entire post, I'm just looking for a pioneer to try again and make a geohot move on Lollipop. And no offense to you, you wouldn't have known this about me anyway, but your kind of information was exactly what I was trying to steer away from. And here it comes, right back at me. I'm just tired and sick of all the people who just do, essentially, a copy/paste of common information. When in my circumstance, am looking for something difference. Again, no harm to you, but anyone and everyone that has ever responded to my threads because it's all the same.
As someone who used to reverse engineer software, updates to said software usually patch those exploits. It's not usually easy to regain a new exploit and can take massive amounts of time. I can't speak for other devs but (at the time I did this stuff and still currently) I have a demanding full time job and a family, which come first over a hobby. I can guarantee I will never buy another Samsung phone again because of this. I know it's not always feasible, but maybe look into getting an HTC phone with developer options that is unlocked from the factory. Venting on here will get your cause nowhere.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Forum is trying to help you!
ElectricBiskitz said:
Well it's pretty obvious that it's AT&T. 5.0 L and Towelroot has never worked before.
Click to expand...
Click to collapse
Right, first things first. Calm down and please stop being so rude and angry when other members who are trying to help you. It's not their fault you are not able to root your phone. It is possible and I'm testament to this.
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.
Besides the fact there are already a metric ass ton of threads in this phone's forum discussing rooting the 900A.
I've been reading them for weeks now after I was overzealous and took the OTA to OC4 figuring there was a root solution already..... There wasn't, and oh well... My fault for not researching first, but it's making me keep my Note 2 until something comes up.
Hell something may already be out, but with rants like yours..... Feel free to enjoy the great advice in the links in my signature.
wwit said:
Right, first things first. Calm down and please stop being so rude and angry when other members who are trying to help you. It's not their fault you are not able to root your phone. It is possible and I'm testament to this.
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.
Click to expand...
Click to collapse
So wait... You have a method to get him from ota 5.0 to a muniz method 5.0? I was under the impression that was not possible once you took the ota ( i didn't, but I'm still curious)
ota 5.0 root?
wwit said:
Right, first things first. Calm down and please stop being so rude and angry when other members who are trying to help you. It's not their fault you are not able to root your phone. It is possible and I'm testament to this.
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.
Click to expand...
Click to collapse
Ok, so I'm sorry if i've got this wrong, but as the user above stated, I too have been scouring the web and FDA searching for a way to root an at&t galaxy s5 with an OTA u5.0 lollipop update. From all the research i have done, I have found no resolution to the locked bootloader. Are you saying that you can root the stock, unrooted, locked bootloader, sm-g900a running lollipop 5.0? If so, I will gladly donate to your Paypal for detailed instructions on how to do this! I am no noob at rooting, having rooted every galaxy since the skyrocket,. But this lollipop crap is driving me crazy. Any help is greatly appreciate!!
wwit said:
Right, first things first. Calm down and please stop being so rude and angry when other members who are trying to help you. It's not their fault you are not able to root your phone. It is possible and I'm testament to this.
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.
Click to expand...
Click to collapse
I need this please! I have an at&t Samsung S5 lollipop 5.0 please guide me
I have not seen any solutions for people who took Ota update. Did you make the exploit yourself? If not can you point out the source?
Thanks!
lowspeed said:
I have not seen any solutions for people who took Ota update. Did you make the exploit yourself? If not can you point out the source?
Thanks!
Click to expand...
Click to collapse
My phone just automatically downloaded the 5.0 update a few weeks ago. I attached a screenshot of my phones specs
I replied to the person who said he has instructions. ..
wwit said:
You need to understand the process of how to do it and you need patients. I live in the UK with an AT&T handset and my handset was never going to ever get to 5.0 because of that fact. I am now on 5.0 and it's rooted and I found out how to do it all on this forum. Further more if you search for my one and only post (yes I'm making you do some work - it's how to teach people to learn new things) I have information in there that shows you how to get to 100% rooted 5.0. What I'm prepared to do is write for you a line by line process in a Word document that will get you from your stock unrooted 5.0 handset to 5.0 rooted. You need the right files and ODIN - that's all you need to complete this. No matter what state you end up getting you handset into bootloop, failed starts..etc as long as you are able to get into download mode you are able to recover the handset. Yes, it can be annoying and yes it can take hours to get back to square one (sometimes) but you have to be prepared for that when you do something like this. It took me two whole evenings and 5 failed attempts before I got it working.
So after reading all this, if you are prepared to accept my help let me know and I will write the document for you.
Click to expand...
Click to collapse
if you're able to root OC4 on a G900A, i'm all ears.
so far i'm unable to install TWRP (fail auth) using odin and it seems it only works for 900F or other models, not 900A specifically that has never been previously rooted. all posts on the topic suggests you cannot downgrade from OC4 and any attempt is futile at the moment.
Rooted 5.0
tmac200913 said:
My phone just automatically downloaded the 5.0 update a few weeks ago. I attached a screenshot of my phones specs
Click to expand...
Click to collapse
Hi, I'm trying to make time to create the document to show how I did it. I intend to recreate the process again on my handset and include screenshots as I go through.
Basically the only way I could get my handset to 5.0 root was to take the handset back to NCE stock firmware (by the way I have all the files on my laptop to do this) using ODIN v3.09. This took my back to G900AUCU1ANCE (4.4.2) April 2014 release. I installed Towelroot, busybox and Safestrap. Did a backup of the device (when I went back to 4.4.2 I then configured my device to look and feel how I wanted it to be because I wanted to restore the data partition once on Lollipop - but this is a required part of the upgrade). You need to use Safestrap to create a backup folder structure on the SD card so you can dump the 5.0 (OC4) rooted backup on to restore later in the upgrade process. I then installed G900AUCU2ANG3 (4.4.2) September 2014 release using Safestrap. I then installed the G900AUCU2AOA1 (4.4.4) February 2015 release and then used Safestrap to take another backup. Then I did an advanced wipe in Safestrap (excluding the SD card) and restored the OC4 rooted backup (I found online I also have this file). Once that restored I then within Safestrap selected the reboot > download mode (don't restart the handset into Lollipop before doing this process - the whole process will fail). Once the handset rebooted into Download mode I connected the handset to ODIN v.3.10.6 and installed the G900A_OC4_Stock_Partitions_wOA1_BL.tar.md5 (using the AP option in ODIN). Once that completed the handset rebooted and after 5-10 mins started to upgrade files. Once that finished the handset was on 5.0 - the same as the screenshot you've posted and it's rooted. I have SuperSU installed working fine and I used Root Checker Basic to confirm the device is rooted. More so I then went on to sideload the G900A_OC4_TetherAddOn so I could get native wifi tethering because AT&T still had this locked down in the root 5.0 I installed above.
anyone verify this?
Not sure they started out on 5.0...I don't know of anyone who has successfully downgraded once on OC4.
wwit said:
Hi, I'm trying to make time to create the document to show how I did it. I intend to recreate the process again on my handset and include screenshots as I go through.
Basically the only way I could get my handset to 5.0 root was to take the handset back to NCE stock firmware (by the way I have all the files on my laptop to do this) using ODIN v3.09. This took my back to G900AUCU1ANCE (4.4.2) April 2014 release. I installed Towelroot, busybox and Safestrap. Did a backup of the device (when I went back to 4.4.2 I then configured my device to look and feel how I wanted it to be because I wanted to restore the data partition once on Lollipop - but this is a required part of the upgrade). You need to use Safestrap to create a backup folder structure on the SD card so you can dump the 5.0 (OC4) rooted backup on to restore later in the upgrade process. I then installed G900AUCU2ANG3 (4.4.2) September 2014 release using Safestrap. I then installed the G900AUCU2AOA1 (4.4.4) February 2015 release and then used Safestrap to take another backup. Then I did an advanced wipe in Safestrap (excluding the SD card) and restored the OC4 rooted backup (I found online I also have this file). Once that restored I then within Safestrap selected the reboot > download mode (don't restart the handset into Lollipop before doing this process - the whole process will fail). Once the handset rebooted into Download mode I connected the handset to ODIN v.3.10.6 and installed the G900A_OC4_Stock_Partitions_wOA1_BL.tar.md5 (using the AP option in ODIN). Once that completed the handset rebooted and after 5-10 mins started to upgrade files. Once that finished the handset was on 5.0 - the same as the screenshot you've posted and it's rooted. I have SuperSU installed working fine and I used Root Checker Basic to confirm the device is rooted. More so I then went on to sideload the G900A_OC4_TetherAddOn so I could get native wifi tethering because AT&T still had this locked down in the root 5.0 I installed above.
Click to expand...
Click to collapse
This is funny.......there seems to be a huge disconnect between this and the actual issue in the OP which is someone that took the 5.0 OTA and wants root access. There currently is no way for him to gain root access. Instead you quoted, almost verbatim, my origina KeepRoot method and files: http://forum.xda-developers.com/showpost.php?p=59996087&postcount=4
muniz_ri said:
This is funny.......there seems to be a huge disconnect between this and the actual issue in the OP which is someone that took the 5.0 OTA and wants root access. There currently is no way for him to gain root access. Instead you quoted, almost verbatim, my origina KeepRoot method and files: http://forum.xda-developers.com/showpost.php?p=59996087&postcount=4
Click to expand...
Click to collapse
Morning, first of all if you take a look at my first post you will see I have clearly stated your name and I have not tried to take credit for your process. Secondly I have only been replying to questions from members who have read my results and have then from my post asked how I did it. I have then simply explained again in the post you have replied to how I got to a rooted version of Lollipop.
Are ypu saying that if a handset takes the ota it is not possible to go back to NCE and then forward right through to rooted Lollipop or are just annoyed thinking I am trying to take credit for your work. I'm happy to guide a member step by step through a process if they want me to but I have already said it's not my discovery.
My note 4 was bought used, no warranty. When I bought it, it was rooted, but no custom rom, worked great. Once lollipop came out, I wiped and returned to non-root and was able to get the update through tmobile. Didn't bother rerooting as things were ok. Marshmallow udpate came, and I noticed a lot of screen lag. Less than a week ago, tmobile did some sort of update and now, the phone shuts off and restarts on it's own, has very slow screen response (nothing, and then tries to do the same function 10 times in a row, messaging is very slow, types the same words several times over). I did a factory re-set twice. Once, I reloaded all my favorite apps, etc. still bad, so then I did factory reset but did not add anything or bring in my contacts, etc. I am planning on buying the note 7 in a 3-4 months, but in the meantime, would like to continue to use my note 4. I tried doing the rooting method using odin, it appeared to work ok (got the successful notice), triggered the knox thing, but..when I use a root checker, it says phone is not rooted. I am hoping that by rooting and putting a new rom on there I can fix this thing in the interim. So..suggestions on what to do next? Let me know what additional information you need. Could it be the phone itself and not the software? Suggestions on a cheap interim phone? links to relevant threads also appreciated. Is there a better way to wipe everything and start new that I am did not do? I did a factory reset. I have two batteries, which I changed out intermittently to see if it as a bad battery. Android version 6.0.1, security patch level july 1, 2016 Kernel 3.10.40-7804088
Knox version 2.6
You need to give more information on what you did to root. What version is your phone, what files did you odin, and did you flash SuperSU?
more info
goosa23 said:
You need to give more information on what you did to root. What version is your phone, what files did you odin, and did you flash SuperSU?
Click to expand...
Click to collapse
No to supersu? it's sm N910t, I think what finally worked what odin 3.9 version and flashed the stock that is meant to go with this particular phone to downgrade it down to lollipop. The first few times, I got fail with Odin, but realized that I had marked the option on the phone to keep it from being wiped/flashed if someone found it, once I got that off, I got a successful message. I used the following link and did all of the things mentioned on a link that I am too newbie to be allowed to post, apparently.
but it goes with 3.7 odin, flash the stock firmware from the phone model, and get to the reset button, if successul and then supersu appears.
I got as far as step 8, with odin showing the green 'reset'. But when I went back to the phone, I did not have supersu.
I've tried to do it again, but I get 'fail'
Try out the toolkit that is in the forum. https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app
The link takes me to a 404 page not found, is part of it missing?
send me the link by private message so i can see what you are doing?
I am coming with hat in hand fully expecting to find out that there is no solution and I am out the $$$ it will cost me to replace. After having this device for close to 2 years, I decided I would root it. I have 5 other devices currently that are rooted and numerous others that I have rooted over the years (including Samsung). Admittedly, I dislike Odin and a lot of other things about rooting Samsung devices. That is part of the reason this was the only device that I ever kept unrooted for more than a month or two. I installed twrp_3.1.0-1_sm-t713_14417n with Odin with no issues. I had SuperSU 2.82 in internal. When I got into TWRP to install it, I saw nothing but directories in internal and it became clear to me that it was encrypted. Attempts to mount, wipe and even reset data all ended up with me booting back to TWRP. I'm sure frustration set in the more things I tried, but now I can't even shut the device down from TWRP or by long pressing power and volume down. Even that just goes back to TWRP. Obviously, I can't get into download mode or system. I just get the recovery booting set warranty bit: recovery message when it starts back up to TWRP. Can't say I have ever seen a device that can't even be forced to shut down, LOL. Thanks in advance if anyone can help.
*I've made some progress. I managed to back door my way into download mode by installing the boot.img from the external SD card. That didn't fix anything, but after that I was able to hold down power down and volume and spam the home button until I got to the download screen. I was able to get back into Odin, but the full firmware file I tried to install errored out at the end with a rev check fail. Hopefully, it was because it thought it was downgrading, so I am downloading the newest file now. The samsung-firware.org D/L is brutally slow. Has a few more hours to go, and I am not positive if it will work yet. Cross your fingers, and throw out any ideas if you have them.
Well, it's alive. Everything is back to normal (except needing to reinstall). Time to root now, LOL!
OK, tried again and ended up restoring the full image again (minus D/L time at least). I am ready to scrap root on this device. I have tried to do everything in the [TWRP 3.1.0-1][ROOT] Galaxy Tab S2(2016) - SM-T713/SM-T719/SM-T813/SM-T819 - 1/4/17 thread. https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627 I would have tried installing no verify, but no matter what I do not see the SU and no verify files on the tablet either after format data without reboot or after rebooting into TWRP. After the format, it shows that data is mounted. Looking at the pictures in the thread, I think maybe it needs the work done on the external SD but the instructions say nothing about that. Time to sleep on it, and maybe someone smarter than me can think of what I might be missing and maybe better step by step instructions are available. At least it is up and running, KNOX trips be damned. I'll post to the TWRP/ROOT thread. BTW, the OS version I am running is XAR-T713XXU2BRB2_T713XAR2BRB2-20180206.
Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.
sliding_billy said:
Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.
Click to expand...
Click to collapse
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk
rholm said:
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
The instructions in the TWRP thread are OK, but they could be a little clearer in some places. Take a look at the interaction between ashyx and I towards the end of the TWRP thread.
https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627
I have two (identical) X4 1900-1 Android One phones , both were rooted with Magisk patched boot image on PPWS29.69-39-6-2. I was able to restore boot image with Magisk Manager on one and the January 1 PPWS29.69-39-6-4 OTA update completed successfully, I reinstalled Magisk per tutorial, root is present and Safetynet passed. The other one became stuck in a kind of updating loop for this OTA prior to restoring the image with Magisk, the update failed on "Step 3 of 6", then starts all over again, ad infinitum, causing battery drain and slowdown. It started this before I restored the boot image with Magisk but fail is continuing since doing so and after a reboot. Automatic updates were turned off in Developer Options, but it still tried to install the update before notifying me that it was available. One difference after restoring boot image with Magisk is that the phone is no longer showing the update progress page--when you tap System Updates the CHecking for Updates flashes briefly and then a toast says Software Update Unsuccessful. That message comes up every few seconds.
My past experience with failed OTA updates on other devices has been the update process stops with one failed update, never tries again and I had to flash manually. Wondering about the best way to address this issue is. One of these phones is my "backup" device, so I have some wiggle room on what to do. Should I (a) flash stock back on the problem phone and let it go through the several security updates, or could I possibly restore a TWRP backup from the updated phone on the problem one? I did a similar restore years ago from one Moto XT926 to another and it worked, but I believe the restored phone might have acquired the serial # of the donor.
I took logcats before and after unrooting, but had trouble uploading one of them. I'll try again.
I spoke a little too soon on the one that "successfully" updated. It is unable to complete phone calls with the same SIM that works in the one that keeps giving the failed update message. Calls just end as soon as send is pressed, or hang trying to connect. In Settings it shows the correct phone number etc., network settings are same as the working phone and this one worked with this SIM a few weeks ago. Some problems connecting to computer visa wifi as well. Beginning to wonder if this is a bad update? Could really use some help here as I don't have a fully functional phone now.
Turns out the "successfully" updated phone is pretty borked. Lots of strange behavior and black screen freezes. The modem/radio seem to have major problems. With no sim card in the phone, the LTE icon shows and indicates signal, but no connectivity. Freezes and blank screens when I hop around in Settings. Wifi connect is wonky. And no phone connectivity with SIM. Looking like I'm gonna have to go back to stock with PPWS29.69-39-6-2, the latest full FW I have.
Has anyone out there had problems with this OTA?
Where can I find the log file from the OTA update, to try and see what went bad?
On the "failed" phone, I was able to find the url for the OTA update (Blur_Version.29.461.4-29.481.10.payton_fi.google_fi.en.US.zip -- PPWS29.69-39-6-4) on the logcat and download it. I've uploaded it to Drive and here is the link is below if anyone needs it. There are lot of error and suspicious messages in one of the logcats from the failed one but interpreting them meaningfully is above my paygrade. I've attached another log to this post. Can someone tell me how to stop the endless updater loop until I can fix the other phone? I am unsure what app/service to disable. I read somewhere there is a way to delay updates on Pie, but it doesn't appear to be a toggle anywhere in Settings.
This is the Android One/Google Fi variant XT1900-1. Flash at own risk!
https://drive.google.com/open?id=151TRLKfmlROCT6f--U4PWRPqmkFyD0T9
The option to force updates is in Developer Options about 10 lines down.
Apparently it defaults to ON.
I have not tested that this would prevent updates since I leave it on, since I want updates.
Force Updates
KrisM22 said:
The option to force updates is in Developer Options about 10 lines down.
Apparently it defaults to ON.
I have not tested that this would prevent updates since I leave it on, since I want updates.
Click to expand...
Click to collapse
Thanks , however that option was turned OFF in Developer Options. Update still forced itself on both phones.
Oh well! It's all google's fault!
Back to stock working so far
KrisM22 said:
Oh well! It's all google's fault!
Click to expand...
Click to collapse
Appears so. Keep reading.
I flashed stock PPWS29.69-39-6-2 and so far things seem to be working--phone, data, wifi.
I'll give a full update on functionality and de-borking when the thing's finished its updates and app installs.
I did notice that in device setup, in the Google Terms the last item "Install updates and apps", states "This device may automatically download and install updates and apps from Google and your device manufacturer...." and there is no on/off toggle!!!! You are forced to accept this "setting", the only option is "Accept"!
Thanks again Google.
I suppose this means that the Developer Options setting is moot.
I would be interested to know if this "(it's not a bug it's a) Feature" is present in Oreo builds?
Remember that google doesn't write android so we can modify it - in fact, google goes WAY out of its way to prevent that - that is why there are so many releases of things like Majisk - google keeps blocking them.
Only a tiny tiny fraction of Moto X4 users attempt any modification of their phones.
You might succeed because you have not yet flashed a custom ROM and thus changed the bootloader and file system from the stock OTA'ed Pie setup. Those that have cannot return. Apparently ever.
KrisM22, would you say that the X4 is a less suitable device than others for rooting? And BTW appreciate your noob warnings, only wish they had appeared sooner. I had already rooted these earlier.
As a matter of practice, I never flash custom ROM or recovery on devices until after they've reached end of OEM support. Actually with the ability to boot TWRP via fastboot I don't see any advantage to installing it but numerous disadvantages. I have unlocked and rooted all my (unlockable) devices, but I may rethink that in light of these recent Android changes. For my next phone I would probably choose a more mod-friendly OEM, if such exists. One+ maybe?
a) you're welcome
b) don't mod this X4 in any way if you are OTA upgraded to Pie.
You might have been able to modify it if it was still on 7 or 8 but I have no idea what the devs are using for
1) bootloader
2)file structiure.
I think, if you have to root, go back to something like a G3, where the bootloader didn't change and the file structure didn't change. Even the Z play had probs around the Oreo bootloader change, but we still could use rsdlite to get back from most disasters.
iow, think pre/pre Treble in any form. It may be, in a couple more years, when Treble has stabilized, that we can get away with modifying things, but on a current phone I would avoid it, UNLESS others have already successfully/repeatedly done it.
I also feel that most of the reason for flashing a custom ROM are gone. People get there, spend a lot of time playing with updates and releases, and eventually go back to stock. There are always a few exceptions, but... As to the various reasons for "needing" root, I feel there are always alternatives. I use Block This! to keep ads out of Brave, BBC app, and APNews app. While there are occasions like can't-edit-build prop, I find I can live without it. It is an adjustment of attitude/expectation. Yes, I have had tons of fun and wasted tons of hours playing with my past phones, it happens I haven't missed it with this one, especially since the sec updates are so recent - I don't worry until it's a year or 2 past.
Once the X4 is on Pie stock, do not modify it in any way.
As to other phones, yes, if you really have to modify it, search the wealth of info that is XDA until you have found a phone that folks have been able to repeatedly get back to stock - be on the lookout for a trail of endless posts about bricked phones and blank flash stuff - a sure sign to avoid it. - This forum is littered with them!
If you have modified a phone: BEFORE taking an OTA, flash phone with latest stock, then let it take the OTA. I had to modify that - I have no idea if you can flash this thing once it is on Pie.
I also feel that most of the reason for flashing a custom ROM are gone.
Click to expand...
Click to collapse
I agree, especially for current devices that are still supported. I'll leave these stock at least until that ends. I actually though it had already reached EOS, so I was caught with my pants down. That said, these phones ran just as well stock/rooted as all of their predecessors I have owned, and as well as when unrooted--until the update fail happened. I may root one if I decide to keep using it beyond EOS. And it's true that most custom ROMs are rarely as smooth and reliable as factory.
Yes, I have had tons of fun and wasted tons of hours playing with my past phones
Click to expand...
Click to collapse
True Dat! But, a hobby is a hobby, and not everything hobbyists do in any field turns out stellar. One reason I always try to have have a decent running backup phone if I mess with a daily driver.
With an EOS device, the risk of a bad outcome is to a large degree mitgated by the greatly diminished value of the device. I have a Moto X 2015 Clark that I've been playing with Randomblame's LOS16 builds on, and it is very usable. Too bad that phone never had good battery life, I liked everything else about it. Might as well keep it rather than sell it for the maybe 50 bucks it might bring. Hell, I only cut my last XT926 loose early last year!
Everything's looking good. After flashing back to stock PPWS29.69-39-6-2, Phone updated OTA to PPWS29.69-39-6-4 and everything appears to be working well. So far no bad residue from past rooting etc.
redwoodie said:
Everything's looking good. After flashing back to stock PPWS29.69-39-6-2, Phone updated OTA to PPWS29.69-39-6-4 and everything appears to be working well. So far no bad residue from past rooting etc.
Click to expand...
Click to collapse
EXCELLENT!!! Great to hear!
Yes, always have a backup!!!
EOS: I was surprised by this update and am now guessing that we might even get one in Mar or Apr. We'll just have to see if that includes 10. But to me a phone is not really "EOS" until maybe a year or 2 after it stops getting updates. I haven't heard of anyone getting hacked. On any phone.
Great!!!
If you are willing, could you do a couple things:
Go to first post edit, go advanced and mark thread as SOLVED.
add a post about how you did it:
1) disclaimer: "Do at your own risk. I am not responsible for anything." or some such!
2. a sentence or 2 about how you did the flash.
3. attach a copy of the bat file you used for the flash.
I think only works if you haven't changed bootloader or file system - NO custom ROM.
Thanks!
Post issue solved etc.
I will happily do that once I've gotten the second X4 straightened out, at that point I'll feel confident it is really "solved".. Probably next week at soonest, I have a minor medical procedure today. I didn't use a .bat file, I fastboot flashed each .img, erase and sparsechunk the old school way. There was a flashall.bat I found on XDA but it was for Oreo builds, had a couple lines in it I was unsure about, and wasn't comfortable modifying it.
Many thanks! Hope all goes well with that today!
If you could provide a log, or list of commands used, that would help!
Update on flashing 2nd X4 back to stock...Flashed PPWS29.69-39-6-2 twice same results: I have wifi/LTE connectivity issues, the wifi constantly connects and disconnects and phone/LTE tries and fails.
There are a couple of threads that discuss similar probles with the X4 and offer various solutions. I may try those, or going back to original Moto Pie ROM or an intermediate build. I also was able to grab the latest Jan. 1 update ROM and that's another option.
The odd thing about this flash is that everything about the phone state was 100% identical to the other X4 that I successfully restored via exact same methods. It would appear that "your mileage may vary" applies. I'll update again when I have new info.
redwoodie said:
Update on flashing 2nd X4 back to stock...Flashed PPWS29.69-39-6-2 twice same results: I have wifi/LTE connectivity issues, the wifi constantly connects and disconnects and phone/LTE tries and fails.
There are a couple of threads that discuss similar probles with the X4 and offer various solutions. I may try those, or going back to original Moto Pie ROM or an intermediate build. I also was able to grab the latest Jan. 1 update ROM and that's another option.
The odd thing about this flash is that everything about the phone state was 100% identical to the other X4 that I successfully restored via exact same methods. It would appear that "your mileage may vary" applies. I'll update again when I have new info.
Click to expand...
Click to collapse
Thanks. modem problems? Dunno... Keep us posted! Thanks!
Are your two One fi, or regular - I bet the motherboards on the two are different, thus the different result.
Both One/Fi. Same baseband versionon both.
Just re-flashed NON-HLOS.bin ad fsg.mbn, same results.
I'm a little baffled by the script commands that follow these flashes to "erase modemst1/t2". One user on this thread claimed omitting (commenting out) those erase commands cured the problem https://forum.xda-developers.com/moto-x4/how-to/android-one-xt1900-1-wifi-sim-stock-t3941837.
I tried the modem flash mentioned above with out the erase commands. No change.
Another suggests:
My XT1900-7 had lost its IMEIs and Wifi connections, even after factory reset.
The solution:
Get XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from lolinet
if you are booting from slot _b, then go to fastboot and flash modem from this FI ROM:
Code:
fastboot flash modem_b NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Click to expand...
Click to collapse
Thinking about flashing back to original stock Pie 29.69-26, or the latest 29.69-39-6-4.